Understanding Bluesky labels
Learn about labelers, subscriptions, self-labels, negation and expiry, and understand the coverage and limits of the Bluesky.bot label inspector.
Sources and subscriptions
A label is a signed statement made by a labeler about an account or record. It contains the labeler's DID (src), subject (uri), value (val) and creation date (cts). Community labels express their authors' opinion; they are not Bluesky's or Bluesky.bot's verdict. People see a community service's labels when they subscribe, according to their own settings.
The inspector separates Bluesky moderation, self-labels, Bluesky.bot and community services. An Automation self-label is an account's own declaration; it does not prove how the account behaves.
How an inspection works
The inspector asks the public AppView using atproto-accept-labelers in batches of 20, with at most four requests at once. The default asks Bluesky moderation, our configured labeler and the 100 most-liked known services. You can request all known services, under a stricter rate limit. No labeler host is contacted directly.
The response header atproto-content-labelers identifies the services actually applied. A service the AppView does not follow may be ignored. Missing coverage is reported explicitly. Our own current labels are also read from the local label log, even when the AppView does not yet follow our service.
Current labels and their effect
The newest label per source, value and subject wins. A newer neg: true removes the label; exp removes expired labels. A post inspection includes its author's labels and its record's self-labels. Label names and definitions use your language when available, then English, then the raw value.
Global labels such as !hide, !warn and !no-unauthenticated have protocol-wide meanings. Adult-content labels may blur media or show warnings. The inspector describes defaults; individual viewing preferences can differ. Read the bot label guide for our service's scope.
Coverage and privacy
The searchable labeler directory is compiled from relay service records and AppView metadata each day. Services not seen for seven days become inactive only after a successful scan. The list does not endorse any service and contains no list of people it labels.
Your input is sent to Bluesky's public API. Answers are cached for ten minutes; failures and ignored services are identified. No label from the services checked does not prove that no labels exist elsewhere. The labeler index date is shown. Inspect an account or post with the label inspector.