Vinny
@hot_town • 6,220 subscribers
Creator @ https://t.co/GUHtBdHMYZ Yapper @ https://t.co/6D664FSp8e
Videos
I tried jack's Buzz. It's like Slack + OpenClaw + Herdr + but with some really unique features that people are sleeping on. The video below shows how it works, and some of my thoughts on the process and platform, e.g.: - Create and interact with agents on top of any harness (claude code, codex, pi, etc.) - Choose which models agents use, including local ones - Agents can delegate work and work in parallel in git worktrees - Agents are first-class citizens and work like humans (creating channels, delegating, access to chat history) - You can share AI compute within a community - It's completely open-source and decentralized Things I like: - Delegating work in chat feels natural: tag an agent, it replies in a thread with status updates as it e.g. compiles, commits, and deploys. - Shared compute: relay owners can share local compute with members, so a community could pool funds for one beefy machine running a local model and everyone uses it. - It's built on Nostr, an open protocol already tied into Bitcoin Lightning so I can imagine communities tipping each other or paying for compute/agent tasks with instant zero-fee micropayments in the future. - It ties together things like OpenClaw, an agent manager, and Slack-style chat into one tool. Things I didn't like: - You can't see what the agent is doing in a terminal. The activity view exists, but if you're used to watching a session run, this UI feels a bit abstracted. A terminal view would be great. - It feels slower than running a session in Claude Code, though no evidence to back that up. For that reason I found myself doing one-off tasks in the terminal instead. Verdict: - I really like it so far and can genuinely imagine working with a team this way. - It doesn't feel ready for big, complex tasks yet. For shallower tasks, it's perfect. - The shared compute + Nostr/Lightning angle is what really separates it from every other agent manager for me, and I think that future is coming.
Vinny1,345,281 次观看 • 22 天前
I took Steve Ruiz's advice & got an ESP32! So much fun for ~$55. I programmed it to display live stats from my online radio station, and use the built-in mic to transcribe and send messages in the station's chat :) Here's everything I bought & how it works: - Waveshare ESP32-S3 1.54" e-Paper AIoT board ($30) - Wi-Fi, mics, speaker, battery charging built in - 3.7V 500mAh LiPo ($10) - JST 1.25 connector adapters ($15 for 20) - ESP32-S3 polls my radio's API over Wi-Fi every 20s → renders a "broadcast console" UI on the 200×200 e-paper - Hold-to-talk: dual mics record → WAV upload → server transcribes w/ OpenAI → posts to the live chat via websocket, pinned as the station owner (API-key auth) - Backend is my Wasp app (React/Node/Prisma) on Railway over 3 tiny endpoints: /status, /chat, /voice-chat - Firmware: PlatformIO + Arduino, GxEPD2 for the display, Waveshare's ES8311 codec drivers for the mic - Runs on battery, fully standalone Built the whole thing in a morning w Claude Fable 5. server endpoints, firmware. A really cool bit was mocking up possible UIs for the esp32 e-paper display using Claude's artifacts. Check out my mixes/shows at
Vinny64,807 次观看 • 12 天前
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.
Vinny92,048 次观看 • 18 天前
I deployed Open SaaS to OpenShip (OpenShip)! It was my first time successfully self-hosting an app on a Hetzner VPS. The video below summarises what it took to get it done, and some of my thoughts on the process and platform, e.g.: - Server: Hetzner CPX22 4GB RAM, 80GB disk, with Ubuntu 24.04 -> $23/month - Create an SSH key locally, add it in Hetzner, and set up firewall rules - Add the server in OpenShip - Buy domain, point it at VPS - Write a Docker Compose file and Dockerfiles so OpenShip would deploy all three parts of Open SaaS stack (react, expressjs, postgres) as one unit - Set Env Vars - Add domain TXT records and get SSL certs Things I like: - Auto-deploy from GitHub pushes. - OpenShip handles domains, certs, and SSL provisioning for you. - Built-in jobs and backups: nightly database backups called out as a genuinely cool feature. - Satisfaction of ending up with a fully self-hosted SaaS. Things I didn't like: - The "$5/month VPS" everyone talks about wasn't actually available in any region. Ended up at $23/month. SAD. - OpenShip is still in beta and I hit multiple bugs. - Deploying anything multi-service isn't a first class citizen on OpenShip yet / requires hand-writing Docker config. - Whether to run your own mail server on a VPS is contested. Verdict: - At $23/month, managed hosting providers still look like better value until you have serious traffic, given how little you have to think about. - Would use it for hobby apps and small projects; wouldn't put an important or high-traffic SaaS on it yet until I trust OpenShip more and understand self-hosting better.
Vinny65,580 次观看 • 24 天前
paid SaaS templates are for suckers. Open SaaS v2 is free, open‑source & way more badass: ✦ sexy ui - shadcn ✦ payments integrated - Stripe Polar ✦ admin dashboard - Plausible Analytics ✦ secure aws s3 file uploads - Amazon Web Services ✦ full cursor rules & llms.txt - Cursor check out the Product Hunt 😸 launch👇
Vinny75,923 次观看 • 1 年前
没有更多内容可加载