Live data from Hacker News

Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting

runtimewire.com

111–120 of 383 posts

Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting

#111
post #101

Earlier quoted context omitted.

No channel will disclose private information. The only way to get that to work is to DM the agent directly or to use slash commands which are ephemeral / private.

so your agents can't access any private information in public channels? Not very useful. Still probably better than Claude's new bot which requires a service account per channel!

Hang on a second. You think accessing private information in a public channel is a good idea?

If a tool is authenticated as personal then it can be only accessed under personal context - i.e. privately. Now if the author of the agent wants to add tools authenticated with shared secrets that is something should be considered in the threat model.

In other words:

- reading my personal emails in a public setting - not ok - reading the agents shared inbox in a public setting - probably ok depending on the threat model

Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting

#113
post #28

> Explain Like I'm 5 > 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.

It’s kinda interesting seeing what, IIRC, was originally a subreddit name which spawned from an AskReddit thread, is now a common marketing phrase in the tech world. Similar to the sub itself, it’s now just shorthand for “describe using the first principles the expected audience should understand.” I imagine a lot of people in the industry also fondly remember the 2010s reddit experience.

I remember someone saying it in high school back in the late 90s or early 00s.

Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting

#114
post #60

That screenshot is some Lynchian horror. "#engineering. New direction, team – we're moving the prototype to Flutter" and then the humans and agent bots engage in flirty emoji-filled chats with cutesy names "I nailed the physics, UI shell @Honeybot?" I'm trying to imagine a world in which this makes sense as a way to organize software development work, but coming up short. It's on a blockchain or something though, so…

It doesn't. But as long as it's a vibe-coded slop product shat out by one of the tech glitterati using the latest marketing wanketeering and sucking up tokens to power the in-built AI nonsense, it'll be eaten up.

The bubble can't pop soon enough.

Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting

#115
post #60

That screenshot is some Lynchian horror. "#engineering. New direction, team – we're moving the prototype to Flutter" and then the humans and agent bots engage in flirty emoji-filled chats with cutesy names "I nailed the physics, UI shell @Honeybot?" I'm trying to imagine a world in which this makes sense as a way to organize software development work, but coming up short. It's on a blockchain or something though, so…

It's also a capture made from seeded test data, all messages are at 5:42. Or a mockup based on said capture.

Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting

#116
post #93

Earlier quoted context omitted.

> so you end up having to write and maintain complex rulesets about what specific resources agents have access to. Why wouldn't you simply use the group chat ID (+more) to key the conversations on?

Because there’s an unlimited number of groups with different combinations of memberships. If I am in group A but not group B and an agent is in both, what is it allowed to share with me?

I'd like to see this problem solved in such a way that your group memberships are transitively applied to your access to agents. In other words: you shouldn’t be allowed to talk to an agent at all if, at a given point in time, that agent is or was in a group that you are not or were not in at that time. Does that make sense? I don’t know how practical this restriction is, but letting the AI manage such permissions on its own seems reckless to me.

Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting

#117

Slack 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?

I'm sympathetic to this POV. I think specifically in the case of Slack, it's not their responsibility in a cosmic sense, but it is in line with the direction and general promise they've been making to customers since forever.

A major part of Slack's go-to-market strategy for as long as I can remember has been pushing Slack as more than a interface for talking with teammates, but as a unified interface for generally piloting your business. Slack has heavily pushed ideas like "SlackOps", they've had Slackbot in the product forever, and they've always prioritized and sold integrations designed to let you build your business workflows in Slack. They even updated Slackbot to go from "that chatbot you DM to set reminders" to "Your AI teammate in Slack": https://slack.com/features/slackbot

So adapting to agents is in keeping with what Slack promises its users. I know that a lot of people don't want more AI features in apps that don't need them (i fall into this camp despite working in ML myself and using LLMs all day). I just think that in the case of Slack, their most passionate power-users are also the sort of people who do really want AI features.

Notion is probably a good companion here. It is similarly a really primitive utility--text editing--that has marketed itself as a sort of central interface for running your company. I know plenty of people, especially outside of engineering, for whom Notion is essentially their browser for work. And it's probably not a coincidence that the Notion + Slack are the two normal office software companies I can think of who've most heavily adopted and marketed AI features.

Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting

#118
post #28

> Explain Like I'm 5 > 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.

It’s kinda interesting seeing what, IIRC, was originally a subreddit name which spawned from an AskReddit thread, is now a common marketing phrase in the tech world. Similar to the sub itself, it’s now just shorthand for “describe using the first principles the expected audience should understand.” I imagine a lot of people in the industry also fondly remember the 2010s reddit experience.

Not sure how long the subreddit has existed but I always assumed it was inspired by the episode of The Office where Michael asks Oscar to explain what a surplus is like he's 5. The broader usage on social media and the ELI5 shorthand are definitely the result of the subreddit though.

This article is definitely abusing the terminology, because I wouldn't expect even tech-knowledgeable people to know what Nostr is or does.

Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting

#119
post #60

That screenshot is some Lynchian horror. "#engineering. New direction, team – we're moving the prototype to Flutter" and then the humans and agent bots engage in flirty emoji-filled chats with cutesy names "I nailed the physics, UI shell @Honeybot?" I'm trying to imagine a world in which this makes sense as a way to organize software development work, but coming up short. It's on a blockchain or something though, so…

Yeah just need to tell the system prompt to not do that. A grumpy senior engineer agent that pushes back on constant tech stack changes would be good too.

Re: Jack Dorsey launches Buzz to combine team chat, AI agents and Git hosting

#120
post #4

[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…

Maybe this is naive or startup-brained of me: I understand not wanting HR-related things to be potentially exposed by a misaligned agent, but when it comes purely to the building of software I personally do not care at all who can read the code/discussions & engage with the process.
Post reply on HN