Loading video...

Video Failed to Load

Go Home

Buzz goes bug hunting. Why wait for bugs to find you when Buzz can find them for you first? My trusted assistant uses the X API to spot bugs reported by Buzz users, analyze them, automatically create tickets in the Buzz Git repo, and share them in our bugs...

42,870 views • 19 days ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

What makes jack's Buzz special is it's built on Nostr. But wtf is Nostr? In the video below I explain why it allows Buzz to do things closed platforms can't, plus an example of building a custom solution on top of it for powerful workflows, e.g.: - Everything in Nostr is just a simple event: id, timestamp, kind, tags, content, signature. - You create an event, sign it, push it to relays. Relays are just servers, and anyone can run one. Buzz creates one for you on startup, or you can host your own. - No central server owns any of it and you can easily follow these events, whether they're from a person, agent, bot, whatever. - The events are the source of truth, not any one app's database, so it's easy to build on. And the openness of it allows improvements to compound. How I publish to Nostr to make Buzz more powerful: - In my last video I had Buzz build an API for our Wasp team tweet dashboard, then hit that API for stats. - This time I flipped it. The app runs a daily job that publishes an event to Nostr, and a Buzz channel subscribes to it. - Every morning our team chat gets the stats: who pulled the most impressions in the last 7 days, what the top tweets were, etc. - Then I tag our agent in the thread like "pull out some recurring themes in our top tweets." It has the whole channel as context and just answers. Why this matters: - To wire my app into our team chat I didn't log into a platform, request API tokens, or install anyone's SDK. I was easily able to get two apps talking through an open protocol instead of an integration. - You're not limited to what a closed-source vendor decides to expose. You can do anything the protocol allows. I love this! - Agents sitting in the channel as members means the data lands where the conversation already is, and they can act on it. Repo for the Nostr app example is on GitHub, link in a comment below.

Vinny

92,048 views • 16 days ago