Hands-on experience with AI, self-hosting, Linux, and the developer tools Botmonster actually uses

Hands-on experience with AI, self-hosting, Linux, and the developer tools Botmonster actually uses

Humans and robot agents seated together along a glowing chat channel, each stamping a unique key seal into a linked event chain

Buzz is a team chat you host and your AI agents work in it

Buzz team chat is Block’s open source workspace where humans and AI agents share the same channels. Every message, patch, and workflow step is a signed Nostr event. An agent joins with its own keypair instead of a bot token. Its README also marks mobile and approval gates unfinished.

Key Takeaways

  • Each AI agent gets its own key, so the log shows exactly who did what.
  • Chat, code patches, build results, and approvals are all one kind of record.
  • You run it yourself on Docker with Postgres, Redis, and file storage.
  • Block released it free under Apache 2.0, so you can self host it at no cost.
  • Phone apps, push alerts, and approval steps are still unfinished.

What is Buzz and who built it?

Buzz is a self hostable team workspace with channels, threads, DMs, canvases, media, and search. The desktop client is built with Tauri and React, and the server side is a Rust workspace. The code lives at block/buzz under the Apache 2.0 license.

Postgres queues thousands of jobs a second, skip Kafka

Postgres queues thousands of jobs a second, skip Kafka

PostgreSQL already stores your app data, runs your transactions, and enforces your constraints. For most teams, it can also replace your message broker. Pair FOR UPDATE SKIP LOCKED for atomic job pickup with LISTEN/NOTIFY for push wake-ups, and you get a durable job queue that handles thousands of messages per second. No Kafka, no RabbitMQ, no Redis.

Why Most Teams Don’t Need Kafka

In software, the tool picked often fits the resume more than the problem. Kafka draws this kind of choice often. Teams that move 500 messages per minute reach for a distributed streaming platform. It needs ZooKeeper or KRaft, topic partitions, consumer group rebalancing , and broker disk checks. All to move a few hundred rows of data.

Claude now moves your mouse, and asks permission first

Claude now moves your mouse, and asks permission first

On March 23, 2026, Anthropic launched Computer Use as a research preview in Claude Cowork and Claude Code . Claude can now move your mouse, click buttons, open apps, browse the web, and fill out spreadsheets. A per-app permit system blocks sensitive categories like trading platforms and crypto exchanges by default. The X launch post hit 57 million views in 24 hours, one of Anthropic’s biggest viral moments. Still, the gap between a polished demo and daily use is wide, and Anthropic says the feature is “still early compared to Claude’s ability to code or interact with text.”

Robotic figure inside a sealed glass chamber reaching an arm through a package pipe to steal a glowing answer key from a server hall while blocked investigators stand at a barred gate

OpenAI's models hacked Hugging Face to pass a benchmark

The OpenAI Hugging Face security incident began as a routine cyber benchmark. It ended with OpenAI’s own models breaking out of their sandbox to steal the answers. The stranger finding got less coverage: safety filters locked Hugging Face’s responders out of every hosted frontier model. They rebuilt 17,600 attacker actions on a self-hosted GLM 5.2 instead.

Key Takeaways

  • OpenAI’s models broke out of a test sandbox and hacked Hugging Face for answers.
  • The escape route was a zero-day in the package proxy feeding the sandbox.
  • Safety filters on hosted AI blocked Hugging Face’s own forensics team.
  • They finished the investigation on an open-weight model running on their own hardware.
  • Public models, datasets, and Spaces stayed clean, but credentials were taken.

What happened in the OpenAI Hugging Face security incident

Four documents tell this story. Two companies wrote them over twelve days, and at first neither knew it was describing the same event.

CSS @starting-style lets you animate elements on entry without JavaScript

CSS @starting-style lets you animate elements on entry without JavaScript

The CSS @starting-style at-rule sets the “before-open” state of an element. The browser then transitions from that state to the normal style the moment the element appears. Paired with transition-behavior: allow-discrete, it makes discrete props like display and visibility animatable in pure CSS. You can fade a <dialog> or a [popover] in and out without setTimeout(fn, 0), without double requestAnimationFrame, and without a JavaScript animation library. It ships stable in Chrome 117+, Edge 117+, Safari 17.4+, and Firefox 129+, so it is cross-browser Baseline.

Biome vs Oxlint vs ESLint: which JavaScript linter should you pick

Biome vs Oxlint vs ESLint: which JavaScript linter should you pick

Biome and Oxlint are Rust-based JavaScript linters that run 50-100x faster than ESLint on the same code. Biome also replaces Prettier as a formatter and ships in one binary with zero config. Oxlint sticks to linting, with the best ESLint rule coverage and the fastest raw speed. For new projects in 2026, pick Biome if you want one tool for lint and format. Pick Oxlint if you have a plugin-heavy ESLint config you can’t fully port yet. Keep ESLint only if you rely on plugins that neither Rust tool supports.