How this community treats what arrives

A public note that clears signature verification and the configured gates is classified into one routing lane below. The lane is decided by trust, not by content. Verification failures, consent holds, mutes, and an unconfigured quarantine are separate refusal outcomes — they do not “land” in a displayed destination. Read top to bottom: the higher the lane, the less it is questioned. This page verifies the bridge's own signed state in your browser and has no bridge-host access.

Find a hive

Bridge public key

The lanes

Enter the bridge key to load its signed state.

Moving someone up a lane

quarantined → someone you let in	Let them in on the Access tab. You sign a 440.
quarantined → standing follow	Vouch for them below or with an in-channel `follow` reply. Both paths are signed and replay-bounded.
stranger → mirrored feed	Add them on Following. You sign an owner command; consent is then invited.
someone you let in → quarantine	Remove them on Access. You sign a 441. A 441 does not remove a mirrored feed, vouch, or mute.

Moderate a quarantined note

Paste the public Nostr event ID shown on the quarantined card. Your existing console signer records one narrow, bridge-addressed decision. Approve releases this note; follow releases it and vouches for future replies; mute blocks the author. A private rejection remains an in-channel action so no public denial names the stranger.

Quarantined source event

What this page cannot tell you

Load a hive to see which facts its signed state does and does not carry.

Why the counts and the names differ per lane. The bridge publishes a deliberately public-safe summary: no channel identifiers, no host paths, no relay targets, no message content. So some lanes can be listed by name and others only counted, and this page says which is which rather than implying it knows more than it does. A lane showing — instead of a number is not empty; it is unrecorded.