Live data from Hacker News

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

runtimewire.com

141–150 of 383 posts

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

#141
post #77
post #26

No one is going to churn Slack for this just because it is "Agent First". Slack is more than good enough to tag Agents and will fill in the missing pieces slowly

Slack's approach is NOT good enough, because the version of the Agent that lives in Slack cannot see the context of the Agent that lives inside Cursor on my developer laptop. They might be clones with identical brains, but they can't talk to each other or compare notes.

So why can't the cursor instance on your laptop have a slack bot? I've had a slack bot on my build machine written in chicken-scheme of all things for years, I feel like the great people (or clankers?) at cursor ought to be able to figure this one out

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

#142

Am I the only one seeing _crazy_ levels of CPU usage when opening the project's homepage ( https://buzz.xyz )? Like "maxing-out-8-cores"-crazy?

the more Tokens/CPU use the better your project. /s

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

#143
post #27

Earlier quoted context omitted.

Any context for the ignorant?

I know that he referred to Twitter as "it's as if they drove a clown car into a gold mine and fell in" Yes Zuck because a product that didn't constantly fuck around with people's privacy settings and had real real-world uses... sure, money is all that matters. You would know. Your vision of the web isn't liberation, it's "dumb fucks", that's all you think people are

I'm old enough to remember when Twitter was a developer centric platform and were emphatically asking developers to use the API tk create products and help spread it. I then remember them rug pulling those APIs and screwing the devs because it interfered with them shuffling the feed and displaying ads and promoted tweets. That was well before Musk and I refuse to see Jack Dorsey as the good guy of tech he seems desperate to present himself as. Especially after he pretended AI was the reason for laying off half of the Block staff

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

#144
post #93

Earlier quoted context omitted.

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…

These kinds of rules never survive real world tests. For example if I create a private group just for myself and auto invite every agent in the company into it, does that mean no one can now use any of them?

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

#145

Earlier quoted context omitted.

Private groups are the worst thing in a truly collaborative environment. Would be nice in Slack to have a Publish this whole freaking thread to a public channel button.

But who is allowed to press it? If anyone, then anyone can expose career ruining messages from someone else, even inadvertently.

Can’t anyone already do that with a screenshot or a log dump? I’m always assuming company provided comms platforms are fully readable by the admins

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

#147
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…

My understanding of what they were saying Buzz is is that agents are "1st class" users in their own right, rather than being an app integration. If you have a user called Claude, then you just apply ACL as normal & you don't care if they're human or bot, right?

The issue is when users interact with claude, what can they see? If the AI can see super-secret-payroll-details.md - is it allowed to discuss that with any user? is there some sort of internal ACL within claude that asks pretty please don't tell everyone they're underpaid?

That's why multiuser agents can be an issue.

The other way to do this, is to have claude installed for everyone, and any user's chat with claude uses their personal permissions via something like oauth delegation or AWS IAM role kinda things. But that, again, is complicated ACL logic living through the delegation of roles and access

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

#149
post #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.

Totally get that for code! But there are orgs where non-code things are compartmentalised — maybe for leak reasons — that still want to employees to make use of agents.

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

#150

Earlier quoted context omitted.

Private groups are the worst thing in a truly collaborative environment. Would be nice in Slack to have a Publish this whole freaking thread to a public channel button.

But who is allowed to press it? If anyone, then anyone can expose career ruining messages from someone else, even inadvertently.

If you wrote it on your company's slack space, it is not really private to the company. Everytime I have a "private" conversation in Slack I have the understanding that the information could be shared. Even now there is a share button not for the whole conversation but yes for individual messages
Post reply on HN