Posted by ryanmerket 7 hours ago
There's a brief write-up on Buzz here https://engineering.block.xyz/blog/buzz
> It’s great and works really well for us, but it raises lots of questions. Does everyone get a bot? If people share one, whose credentials does it use?
Eventually you throw in this admission in the middle of other stuff:
> Buzz gives each agent its own key. The agent’s owner signs a narrowly scoped authorization. The agent then signs its own work with its own identity.
So you're explicitly picking a bot per person, you're just calling them an agent. But you never really admit this because you call it 'an agent' rather than "the user's agent". You're still ending up with lots of agents each owned by people, you're just writing another orchestration layer yourself.
> The agent remains the author. Its credential proves who authorized it and under what conditions.
Right yeh, so the human is the responsible party.
> If an agent key leaks, revoke the agent without replacing the human identity behind it.
Just like you revoke an app-key on GitHub/Slack. This isn't a revolutionary thing you're doing.
You then throw in this curveball.
> Buzz can also run an agent’s model requests on another community member’s machine.
How? How is this resource managed or limited? Do I have to assume Buzz will just borrow my laptop's CPU & GPU at random?
> So you're explicitly picking a bot per person, you're just calling them an agent. But you never really admit this because you call it 'an agent' rather than "the user's agent". You're still ending up with lots of agents each owned by people, you're just writing another orchestration layer yourself.
Giving everyone their own agent/bot/app in Slack is nontrivial because of how Slack apps work. If you're okay with them impersonating you, it's easy, but that's weird and I don't like having to guess/discern if I'm talking to you or a bot wearing your face
> How? How is this resource managed or limited? Do I have to assume Buzz will just borrow my laptop's CPU & GPU at random?
This is opt in. It's an integration with https://github.com/Mesh-LLM/mesh-llm that scopes shared compute to your Buzz community. This is very early right now and we're working to get it right. But the idea of a totally self-sovereign, self-hosted community providing its own inference is exciting.
Though I fear this might not be well maintained or have a good foundation being so heavily agent focused but I will out of sheer ambition of a more open stack support anything that help make it a possibility.
Also the git hosting stuff seems a bit sus tbh.
I wonder how they plan to make mobile work, and it's amusing going with an xyz domain given their reputation.
I'd like to think if I were JD that I would be focusing on something a bit more tangible for the world. A more useful aspect of tech to emerge or be invested in.
But, apparently AI agents in chat that sit adjacent to code is The Next Big Thing?
there's definitely room for someone to do it right.
i'm skeptical if it'll be dorsey, however.