Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting
21–30 of 383 posts
Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting
#22Slack 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?
Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting
#23Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting
#24Marketing bullshit aside, this is just bots in chat rooms, right? Am I the crazy one?
Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting
#25Slack 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?
Technically, because if the world moves to AI-driven tools and Slack is not cooperating, it will no longer serve the world and will be left behind.
> Isn't a tool supposed to work for you
If you want AI integration in your chat and Slack is not helping make it happen, then Slack is not working for you.
On the other hand, constantly chasing the latest fad can be a useless drain of resources and (worse yet) attention. In this context, AI is by now most likely not a fad, but the ways to interoperate with it can be: mcp, cli, agent, tag, ... And the same goes for users, reinventing their processes and practices 5 times per year.
Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting
#26Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting
#27As much as I detest Zuck, he was right about Twitter guys.
Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting
#28> Buzz is an open-source, self-hosted workspace that combines team chat, AI agents and Git hosting using signed Nostr events, so teams can keep control of their data.
Very different expectations of 5-year-olds.
Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting
#29Slack 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?
Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting
#30[I work for Slack, opinions very much my own] Having agents see everything you and your colleagues see is cool. The challenge comes when you want to make certain things private to certain people. In that world you don’t want multiplayer agents leaking data, so you end up having to write and maintain complex rulesets about what specific resources agents have access to. Single-player agents, on the other hand, are much…