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

91–100 of 383 posts

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

#91

Post by _pdp_ »

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…

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 agents are very strong this department and it is guaranteed there is zero leak of private information.

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

#93

Post by paxys »

GodelNumbering wrote: post #47
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…

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

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

#94

Post by jacobgold »

verdverm wrote: post #41
jacobgold wrote: post #9

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…

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...

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

#95

Post by _pdp_ »

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.

It is safe bet to assume that all of them are generated with LLMs.

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

#96

Post by [deleted] »

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…

[deleted]

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

#98

Post by datadrivenangel »

_pdp_ wrote: post #91
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…

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.

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

#99

Post by breuleux »

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.

The phrase was in an episode of The Office prior to that. I think it's fairly old.

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

#100

Post by zackham »

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…

all ingested data and all derivations of that data can link to source channel and associated ACL that syncs with the source. then search/reads/etc just join on and respect the ACL. not that complicated to manage for things like slack, meetings, etc.
Post reply on HN