31–40 of 383 posts
The project fell to the back burner because I had VM ambitions and just didn't have enough disk space on my macbook to do VMs well. 512 GB and always full
Earlier quoted context omitted.
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?
It’s not Slack’s responsibility to do so, but it is their vulnerability if they don’t
Earlier quoted context omitted.
I think you're crazy. It's not just bots in chat rooms, it's bots in chat room with an AI Investor Hype Money™
Kind of amazing that given the state of the world money is still focused on remixes of different forms of social engagement. Is this because it's an obvious place to display ads? Or is it something else? I'd like to think if I were JD that I would be focusing on something a bit more tangible for the world. A more useful aspect of tech to emerge or be invested in. But, apparently AI agents in chat that sit adjacent to…
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.
IF yes, I clone it and point my LLM at it to do whatever I need it to do.
You're think with your cloud-LLM brain; maybe buy a good GPU and download a local model and you too can-do attitude!
As much as I detest Zuck, he was right about Twitter guys.
Jack: Twitter, Square (Block), Bluesky/ATProto, bitchat (interesting), buzz (we will see). He just always fumbles the 1 to N (See Vine as an example)
Other Twitter Guy: Medium
Zuck: PHP dev, gets a hit, reads innovators dilemma... buys instagram. Everything else sucks.
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…
[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…
We started with Slack. This kind of works but dialing in the gazillion of permissions needed to end up with something that works is a bit painful. And you have to do this over and over again for each new bot.
So, we started experimenting with self hosted alternatives. First we tried Matrix. It's nice but a bit too strict on end to end encryption which gets in the way if you actually want to share information with bots. So, a few weeks ago we switched to Zulip. That's pretty straightforward to setup as well. It's very easy to create bot users with both and create some automations. We did some with Openclaw and I ended up replacing those with something coded around the haystack framework, which is a bit less of a messy basket case than Openclaw.
And as I discovered after I installed it, the Zulip leadership actually just got hired by Anthropic. It seems Jack Dorsey beat them to market making some announcements but I imagine that Anthropic might have very similar plans.
IMHO team level use cases for agents actually make a lot of sense. Companies are run by groups of people and the larger those groups the more team overhead you get. Perfect for optimizing with AI. And if you have people doing a lot of stuff with AI, that only adds to the need for them to communicate what they are doing and coordinating with others. Doing that out in the open in some shared channel makes a lot of sense. And having some shared team guard rails also makes sense. And if you think about more complex processes with handoffs between people (and possibly some agents), a team chat is a good place to do those as well.
It's crazy how one lucky break lets somebody spend the rest of their life throwing s*t at the wall to see what sticks to earn them more money.
The "Zuckerberg Method".
He wasn't the first, and won't be the last, but I'm pretty sure he has thrown the most shit.
Google Buzz [1] along with Wave you both were too soon for this world. 1. https://en.wikipedia.org/wiki/Google_Buzz