Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

runtimewire.com

Post reply on HN
Print view View original

101–110 of 383 posts

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

#101

Post by _pdp_ »

datadrivenangel wrote: post #98
_pdp_ wrote: post #91

Earlier quoted context omitted.

I agree with what you are saying but this is not how we solved the issue with who can access what. In our cloud harness we have the notion of shared and private secrets. When something is authenticated with a shared secret it is basically something that can be used in a public setting. If something is private then it can be only accessed via trusted channel. It works for slack, telegram, etc. In fact, our slack agent…

And if someone gets access to a channel that they shouldn't? The best norms around slack channels is to have most channels be public, but have norms where not everyone is in every channel.

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.

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

#102

Post by overgard »

Gecko4072 wrote: post #3

Now when I see new software projects I just think of how much of them are made with agents and the unreliability/easy abandonment that comes with it. Ten years ago this product would have been of a known quality. Not saying anything about buzz specifically.

Yeah, it used to be the friction of making something was at least a partial sign that it had been thought out to some degree. Now it's just "lets lob it on users and make them figure out if this is worth a damn". I feel like with a lot of this stuff, there isn't much value to being an early adopter and there's a lot of risk. Better just to wait a couple months to see how things shake out. If it has staying power it really won't matter if you're behind by like a few months.

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

#103

Post by butlike »

mplewis wrote: post #15
Gecko4072 wrote: post #3

Now when I see new software projects I just think of how much of them are made with agents and the unreliability/easy abandonment that comes with it. Ten years ago this product would have been of a known quality. Not saying anything about buzz specifically.

oh, you absolutely know this one is going to be a slopfest. Buzz is going to make GitHub look like a paragon of nines.

It's probably just Dorsey's vibe-coded side project. The scope isn't too big and it's rather unimpressive

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

#104

Post by hibikir »

datadrivenangel wrote: post #98
_pdp_ wrote: post #91

Earlier quoted context omitted.

I agree with what you are saying but this is not how we solved the issue with who can access what. In our cloud harness we have the notion of shared and private secrets. When something is authenticated with a shared secret it is basically something that can be used in a public setting. If something is private then it can be only accessed via trusted channel. It works for slack, telegram, etc. In fact, our slack agent…

And if someone gets access to a channel that they shouldn't? The best norms around slack channels is to have most channels be public, but have norms where not everyone is in every channel.

I have lived in organizations where under 1% of messages were made on public channels. The experience of finding information in slack, or even knowing if there's a private channel where all of this is discussed, but where nobody invited you to, is not one I wish on anyone.

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

#105

Post by designerarvid »

baron3dl wrote: post #90
sulam wrote: post #79

I 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 solves for who owns the shared service. nobody. run your own, use an open relay, or pay for one from folks you trust.

What problem is that a solution to? Is there a problem with someone owning it, in that case: what?

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

#106

Post by hacker_88 »

joenot443 wrote: post #81
rsstack wrote: 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.

Are you smarter than a five year old, kinda show

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

#107

Post by kccqzy »

Gecko4072 wrote: post #3

Now when I see new software projects I just think of how much of them are made with agents and the unreliability/easy abandonment that comes with it. Ten years ago this product would have been of a known quality. Not saying anything about buzz specifically.

Nah. I made plenty of software and then abandoned them because I lost interest in them. My GitHub is already a fairly large collection of my own abandoned software, and there are 10x more on my PC that I never bothered to upload to GitHub.

Easy abandonment is always there.

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

#108

Post by datadrivenangel »

_pdp_ wrote: post #101
datadrivenangel wrote: post #98

Earlier quoted context omitted.

And if someone gets access to a channel that they shouldn't? The best norms around slack channels is to have most channels be public, but have norms where not everyone is in every channel.

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!

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

#109

Post by verdverm »

jacobgold wrote: post #94
verdverm wrote: post #41

Earlier quoted context omitted.

ATProto's tbd permission system is insufficient for the granularity needed in enterprise. Many of those features needed (like groups) will have to be built in an app view and by proxy be centralized. ACLs are two generations in the past of IAM history Chat is also not a great modality for the PDS/ATP, Roomy learned this and is building a dedicated protocol and bridge.

There's a new feature being added to AT to support "permissioned data" that would handle a Slack-like use-case: https://github.com/bluesky-social/proposals/tree/main/0016-p...

I know about it, that's the one I'm referring to. That proposal is insufficient. I was deeply involved in the private data discussions, built a PDS fork / prototype on ReBAC/SpiceDB, and presented it at the first Private Data WG (which no one from Bluesky attended). Bluesky has chosen a path that suits them, not the community at large.

You can learn more about my work here: https://github.com/verdverm/atproto

the community convos here: https://discourse.atprotocol.community/tag/private-data/2

At this point, Bluesky controls the protocol, decided what they want permissioned spaces to look like, and are not entertaining any other proposals (afaict).

I expect there to be an eventual successor that puts permissions at the core of the protocol from the very start.

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

#110

Post by swader999 »

muglug wrote: 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…

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.
Post reply on HN