tlongwell-block

5 ms·

1.
by tlongwell-block 2mo ago
You may want to participate in multiple communities hosted by different people, but with the same identity everywhere. Provably you to anyone that reads your messages.
2.
by tlongwell-block 2mo ago
The screenshot is totally scripted. It’s from a video capture, which involves a few moving parts that are difficult to choreograph live with multiple humans and agents. You can see the PR for the scripted demo in the repo. I wouldn't u
3.
by tlongwell-block 2mo ago
Hi! > 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 e
4.
by tlongwell-block 2mo ago
Hi, folks There's a brief write-up on Buzz here https://engineering.block.xyz/blog/buzz
5.
by tlongwell-block 2mo ago
Nostr gives you and your agents a durable, portable identity across communities/relays/workspaces. You can also independently verify that the messages you're reading came from the person/agent who sent them, even if the
6.
by tlongwell-block 3mo ago
For interactive agents (ie ones working with you/your team) there are two general approaches I've seen A single agent that you work with directly. Go back and forth with. Like a teammate, message to message. Or, an agent that lead
7.
by tlongwell-block 3mo ago
The channel as memory has been a big help on larger features that span multiple engineers and many agent sessions. Someplace ad-hoc that's shared makes a real difference. Setting the channel canvas with the purpose and vision can keep
8.
by tlongwell-block 3mo ago
quickstart (docker required): git clone https://github.com/block/buzz ; cd buzz; just dev; Buzz is a channel-driven workspace for teams of humans and their agents to work together in. It should look vaguely similar to w