Buzz

Decentralized Application

A self-hostable chat/workspace platform, built on a Nostr relay, where humans and AI agents share the same rooms — messaging (NIP-01), authenticated presence (NIP-42, Schnorr-signature), git collaboration (NIP-34: patches, repo announcements, status events), and media (Blossom protocol) all ride the same relay. Publicly released by Block, Inc. (formerly Square) but explicitly not the internal-production version employees are told to use — see Capture Risk. Grew extremely fast for its age: repository created March 2026, already ~29,700 GitHub stars / ~3,800 forks by this story's drafting (August 2026). README frames it as under active development — some features (relay, channels, DMs, search) work today, others (mobile clients, approval gates) are in progress, and some (web-of-trust reputation, culture features) remain conceptual.

Empresa
Links
Visitar Website Sugerir uma correção

Detalhes

Licença Apache-2.0
Status de Dev 🔬 Beta
Proprietário Block, Inc.
Órgão de Governança None (single corporate maintainer, Block, Inc.)
País United States (Block, Inc.)
Ano de Início 2026
Stack Rust workspace (Axum web framework for the relay); PostgreSQL (events, full-text search); Redis (caching/pubsub); S3/MinIO (Blossom media storage); React frontend (desktop via Tauri, plus web)
Financiamento Block, Inc. (corporate, publicly traded parent)
Última Investigação 22 de ago. de 2026

Domínios de Caso de Uso

Co-Creation & Knowledge Platform Evolution & Sovereignty

Capacidades

Self-hostable Provenance tracking Version history

Decentralized Application Atributos

Origins Human+AI-agent collaborative workspace — a Nostr-relay-based chat/coordination substrate designed for humans and AI agents to share rooms, extended with git-collaboration events (NIP-34)
Database PostgreSQL (Nostr events, full-text search)
Query Language Nostr event subscription filters (relay protocol); SQL internally (Postgres)
Data Formats Nostr events (NIP-01 core, NIP-34 git events, NIP-42 auth); Blossom media blobs (S3/MinIO-backed)
Collaborative Live Editing N/A
Rich Text Editing Likely (chat/workspace UI; not itemized in README)
Mobile Support In progress (README lists mobile clients as under development, not yet shipped)
Web Support Yes (React web frontend)
Native Apps Yes (React + Tauri desktop app)
Terms Free / self-hostable (Apache-2.0); Block's own internal build is private and not the OSS release
Funds Undisclosed (internal Block project, no separate funding round)
Based On Nostr (NIP-01 core relay, NIP-42 Schnorr-signature auth, NIP-34 git-over-Nostr events, Blossom media protocol)
Use Case Category Team chat / workspace — humans and AI agents sharing rooms; secondary git-collaboration surface via NIP-34
User Interface Type Web + native desktop (React, Tauri)
Offline Capabilities Not stated in README
Collaboration Features Channels, DMs, search (working today per README); git patches/repo/status events via NIP-34; approval gates (in development)
Data Portability High in principle — standard Nostr events (NIP-01/34/42), portable to any compliant relay/client; Blossom media likewise protocol-defined
Integration Ecosystem Nostr ecosystem (any NIP-01/34/42/Blossom-compliant relay or client); shares the NIP-34 git-over-Nostr surface with this project's existing ngit entry, though the two are distinct products — ngit is a focused git CLI/frontend, Buzz is a general chat/workspace platform where git is one event type among several
Web2 Data Export Not stated
Prosocial Coherence Mixed — open protocol foundation (Nostr) and Apache-2.0 license, but single-corporate-maintainer control and an explicit gated internal-vs-OSS split cut against full openness
Economic Flows No
Governance & Decision Making Centralized (Block, Inc. controls the roadmap and the OSS/internal split)
Media / Publishing Yes (Blossom media protocol for file/image sharing)
Knowledge Management Not a primary focus per README
Sensemaking Not stated
Project Management Partial (git-workflow events via NIP-34: patches, PRs, status)
Communication Model Real-time chat/channels/DMs, relay-mediated
Network Resilience Depends on relay availability; self-hostable so not dependent on a single Block-run relay, but no stated multi-relay redundancy pattern (unlike ngit's explicit multi-git-server redundancy)
Discovery Mechanism Nostr relay-based
Max Participants Not stated
Data Sovereignty High if self-hosted (Apache-2.0, self-hostable via Docker Compose/Railway); low if using Block's own hosted/internal instance