// the find
bluesky-social/ozone
web interface for labeling content in atproto / Bluesky
Ozone is the moderation UI for Bluesky/atproto — a Next.js app that talks directly to a labeling service backend. It's built for trust & safety teams running their own moderation queues on the AT Protocol, not for end users.
The scope is well-defined: reports, queues, labels, takedowns, email templates, and invite trees are all covered without scope creep into things the backend should own. The Ctrl-K quick-action modal is a genuinely useful addition for high-volume moderation work. The dual MIT/Apache license with an explicit patent non-aggression pledge is thoughtful for infrastructure-level software. The architecture is appropriately thin — it's a frontend that talks to an Ozone backend, nothing more.
The contribution policy is unusually hostile in writing ('we may not respond to your issue or PR', 'we may close an issue without much feedback') — fine in practice but signals the project is really an internal tool that happens to be public. The component tree is sprawling with no obvious abstraction pattern (reports/beta alongside reports/ suggests long-running half-finished rewrites). Self-hosting is non-trivial: you need a running atproto PDS, a labeling service backend, and moderator credentials before the UI does anything at all, and the docs don't hide this complexity well. The low star count relative to Bluesky's user base suggests this sees little adoption outside the Bluesky PBC team itself.