thearchivist.fun
Historical record · 2024-03-12

Ozone makes community labeling a shared moderation tool

Bluesky released Ozone as open-source software on 12 March 2024. The collaborative tool lets a team inspect reports and apply labels to accounts or individual pieces of content. The accompanying announcement described independent moderation services that people could subscribe to in addition to the moderation required by the Bluesky application. The distinction between removal and labeling is central. A host can decide what it stores, while a label can inform how an application presents something to a viewer. A community might prefer a warning, a hidden post or a particular classification without making that preference the rule for every other community. The system separates a judgment about content from at least some of the decisions about how that judgment is displayed. Ozone also addressed a mundane sustainability problem: moderation work often becomes attached to one person's account. A shared reporting queue and a service managed by several people can distribute that burden and make handover easier. This is an organizational feature as much as a software feature. Open code alone does not recruit reviewers, establish appeal procedures or pay for ongoing work. For researchers, the release creates a useful case study in layered governance. The official app still has baseline rules; subscribing to another labeler does not remove them. A label also represents the decision of a specific service, not an objective property that exists independently of its definitions and review process. When citing a moderation outcome, record the label, the service applying it, the time and the relevant policy. That level of detail allows later comparison if a label changes, an appeal succeeds or another service reaches a different conclusion.

Context and provenance

A moderation screenshot can conceal the chain of decisions behind what is visible. One person may see a warning while another sees the same post normally because their subscriptions or preferences differ. This is why moderation history should preserve policy text and interface state alongside the content itself. The Ozone release also invites a practical question for community projects: can another trusted person take over the work without breaking the service? Shared ownership, documented criteria and an understandable report queue are valuable even in a small archive with no elaborate automated system. The human maintenance task remains part of the design.

Why it matters

The release made labeling and collaborative review reusable parts of community governance rather than only internal platform machinery.

Sources and evidence

  1. Bluesky: Stackable Approach to Moderation
  2. Bluesky: Composable Moderation

Editorial review: 2026-09-23. New evidence may change this account.

Report a problem with this record