pretty interesting that cloud data is not covered by the 4th amendment. I wonder if we’ll push for on-prem storage of context and memories as our relationship with AI gets more personal and intertwined.
The article states that OpenAI only discloses user content with a search warrant. How did that lead you to believe that it's not subject to the fourth amendment?
I still haven't once talked to an LLM for personal reasons. It's always been to get information.
Talking to an LLM like a human is like talking to a mirror. You're just shaping their responses based on what you say. Quite sad to see stuff like the "myboyfriendisai" reddit
We built this because we were frustrated with Apple's lack of AI features in Siri.
It basically allows you to use AI to monitor, navigate, control and execute tasks across any iOS native app. You can give instructions via voice or create custom workflows for repetitive tasks.
Happy to answer any further questions and comments.
I read the article but have yet to understand why someone would want to use a framework that introduces meaningless abstractions that are not properly documented or well maintained -aka, they often introduce breaking changes.
I’m interested in a useful agentic framework but LangGraph doesn’t seem to cut it.
Agreed if you are building a typical service. The abstractions will slow you down and don’t and anything.
The use case where they are helpful is “bring your own keys” apps. I maintain https://github.com/kiln-ai/kiln which allows you to bring keys for 13 different providers. The abstraction is very much worth it for me.
That said:
- I migrated from LangChain to LiteLLM and never looked back
- I have over 1000 automated integration tests that check the grid of LLM features (tools, json), model, and provider. Without them it would still be a mess.
fully agree that LangChain is a meaningless abstraction but I've found that the graph abstraction that LangGraph uses is a very useful mental model for thinking about an agentic flow
For what LangChain does, most of the time I see no need for any framework. I would rather directly work with a vendor's official package. LangGraph is different. It is a legitimate piece of workflow software and not a wrapper framework. Now, when it comes to workflow there are many other well established engines out there that I will consider first.
I think the main thing LangGraph adds is a state machine framework for human in the loop with time travel.
So if you have an authoring workflow where a doc goes through a bunch of steps, and at some steps the analyst might want to fix some LLM output manually, and try a couple of things and then go back to the way it was before and try again, it will do that and you won't have to make your own state machine.
LangGraph implements a variant of the Pregel/BSP algorithm for orchestrating workflows with cycles (ie. not DAGs) and parallelism without data races. You can design your graph as a state machine if you so desire
By that definition Elizer should be working on really hardcore stuff, right? And yet his explanations about actual technical stuff come across as a guy that barely understands how matmul works.
Came here to +1 on the likelihood of transition thoughts and the discovery of procreate.
I also happened to gift an iPad Pro to my wife. Her daily workflow for work are apps like gdocs and buffer and the ipad handles that just fine. I think we underestimate how similar is the regular job workflow and overestimate the particular setup we need for programming / engineering.
And for digital art, she started from 0 and is now a pro at ClipStudio art and Procreate. She is working on her webtoon and has created plenty of nfts and twitter profile pictures on fiverr. I’ve started bringing an ipad to engineering lectures since it has also helped me
a great deal with note taking.
reply