This is an interesting step in a fairly obvious direction.
I wonder how they plan to make mobile work, and it's amusing going with an xyz domain given their reputation.
Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting
121–130 of 383 posts
Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting
#122Very interesting!
As a small startup I'd love to ditch Slack, as its a walled garden and both under-featured and over-complicated at the same time. GitHub has been losing my favor too.
Tangentially our startups is combining email, AI agents (chat and coding), and GitHub workflows and it feels really good.
https://housecat.com/blog/gmail-durable-workflows-sandbox-vm
It feels like a renaissance for all workspace tools, where up until recently it was mostly dev tools that got all the really fun power ups.
Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting
#123[flagged]
Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting
#124Disclaimer that I used to work at Slack
I love that we're challenging the status quo in chat. It feels like we've settled into an eternal September of sorts. I am somewhat bearish that Slack and Teams will survive, or rise to, the agent era.
That said, I'm curious whether NOSTR is really the protocol for this. For some really large corporations you're looking at a lot of clients (and their shadows like cellphones, local agents etc) as well as a lot of (likely) team-based agents.
The identity architecture makes sense for centrally hosted agents. Users also probably have their own personal agents as well. Do those just reuse user credentials or are they differentiated in some way? I couldn't tell.
I also am curious whether git really needs to be a dependency here. Like, maybe for Block it does, but it introduces a lot of complexity that I feel could be exported to merging VCS Host events to the Buzz event log.
I'm also curious what challenges will arise as new capabilities emerge. For instance, both Sol and Claude can now render native components in my chat window which is a massive leg up in terms of firming up a design change.
Rust is also a choice. I'm curious what alternatives the team considered and how they landed on Rust.
Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting
#125Disclaimer that I used to work at Slack I love that we're challenging the status quo in chat. It feels like we've settled into an eternal September of sorts. I am somewhat bearish that Slack and Teams will survive, or rise to, the agent era. That said, I'm curious whether NOSTR is really the protocol for this. For some really large corporations you're looking at a lot of clients (and their shadows like cellphones, lo…
Shared information like code and files are increasingly important for keeping people and agents aligned, and "AI Native" businesses will become even more code heavy, so that makes sense.
Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting
#126washed.xyz was taken
Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting
#127I feel like this might be solving a real problem (agents having identity, access controls, etc that are provisioned like you would a regular user) — with this Nostr layer that doesn’t really provide any specific value that I can see. So actions are signed, great — this is like telling me I’m going to be using blockchain to store my files because I need crypto on top of my crypto. We see where that ended up. Is Nostr…
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 server/relay operator is broken or trying to trick you.
This can be important in environments that live outside of enterprise auth walled gardens.
Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting
#128Slack exists largely because IRC was insufficient. It didn't natively support channel history, search, etc. For AI agents to flourish, Slack has to either truly open its network with a protocol or eventually be replaced. I'd like to see Slack embrace an AT protocol-based chat system, which then apps like Buzz could implement. Then users could log in with domain handles like @yourname.com, and agents could use handles…
Why is it Slack's responsibility to help agents flourish? I ask about Slack here because it's pertinent, but I've both seen and experienced firsthand this inversion across the industry where we must adapt our workflows for AI. Isn't a tool supposed to work for you, not the other around?
It is like asking in 1999 why DHL should have a website. Surely they can just meet people where they are - on the phone, on the high street. Why does everything need a bloody website.
Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting
#129[dead]
Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting
#130Earlier quoted context omitted.
It’s not Slack’s responsibility to do so, but it is their vulnerability if they don’t
You're assuming there is a bag to capture about placating to slop bots, that has yet to be determine. What it mostly seems to do now is balloon your services capacity on serving your worst customers to do busy work no one cares about.
Slack isn't responsible for the work product of its customers. They provide a service, and like to get new customers. Those customers use agents. Which tech solution they use is debatable but they can't ignore it. They have supported bots and 3rd parties for eons anyway.