bitvid/docs/moderation

bitvid Moderation Overview

What we’re building

bitvid is follow-centric. Your Home feed comes from people you follow (F1). Discovery can optionally expand to friends-of-friends (F2) and ranked sources. Moderation is client-side and user-controlled with optional admin lists.

Core principles

• Freedom to choose: User picks filters. Defaults are safe but reversible.
• Explain decisions: Every blur/hide shows a “why” badge and a “show anyway” control.
• Whitelist > blacklist: Prefer showing content from trusted networks over fighting global spam.
• Minimal central power: Admin lists are opt-in; users can unsubscribe.

Threat model (short)

• Spam/bots, impersonation, malware, NSFW thumbnails, illegal content, brigading/dogpiles, Sybil report attacks.

Building blocks (Nostr)

• Reports: NIP-56 (kind 1984) with types like nudity, spam, illegal, impersonation, etc.
• Lists: NIP-51 (mute list 10000, categorized people 30000, bookmarks 30001).
• Replies/threads: NIP-10 (comments).
• Counts: NIP-45 (relay COUNT; optional fallbacks).

Runtime flow (blur, hide, override)

• ModerationService orchestrates ingest and scoring. Review the service for the trusted-report math and helper entry points.
• createModerationStage wires the service into the feed engine where moderation summaries decorate timeline items.
• bitvidApp.decorateVideoModeration connects stage output to the UI layer alongside feature-flag plumbing.
• VideoCard.refreshModerationUi applies badges, blur states, and "show anyway" toggles.

Where to extend

Thread new moderation behaviors through the same service → stage → app → UI flow above. Extending the existing layers keeps overrides, feature flags, and QA hooks consistent—avoid spinning up parallel moderation modules unless the architecture document explicitly calls for it.

Defaults (policy)

• Blur video thumbnails if ≥ 3 F1 friends report nudity.
• Disable autoplay preview if ≥ 2 F1 friends report nudity.
• Downrank author when any F1 has them in mute list (10000).
• Opt-in admin lists (30000 with d=bitvid:admin:*) can hard-hide content.

You can override all defaults in Settings → Safety & Moderation.

Community blacklist federation

Operators can delegate hard-hide decisions to trusted curators without giving them full admin powers. The flow is:

1. The super admin maintains a kind 30000 list with d=${ADMIN_LIST_NAMESPACE}:${ADMIN_COMMUNITY_BLACKLIST_SOURCES}. Each a tag references a community curator’s blacklist as 30000:<curator hex pubkey>:${ADMIN_LIST_NAMESPACE}:${ADMIN_COMMUNITY_BLACKLIST_PREFIX}:<slug>.
2. Every curator publishes their own kind 30000 list using the referenced d tag (${ADMIN_LIST_NAMESPACE}:${ADMIN_COMMUNITY_BLACKLIST_PREFIX}:<slug>) and fills it with p tags for accounts they want hidden.
3. bitvid automatically fetches each referenced list, merges the entries into the global blacklist, and removes any duplicates or guard-protected accounts (super admin, editors, or whitelist members).

To add a community list, append a new a tag to the super-admin source list and ask the curator to publish their companion p list. To remove a list, delete the a tag or ask the curator to clear their p entries; the client stops ingesting it on the next refresh.

Safety & Moderation controls

The profile modal now exposes the blur and autoplay thresholds so operators can dial in stricter or more permissive behavior. Enter a non-negative whole number to override the default or leave the field blank to fall back to the baseline values above. Adjustments are stored locally, applied immediately to the active feed, and rehydrate on every load.

Files in this folder

• web-of-trust.md — how we compute trust signals and thresholds
• nips.md — exact NIPs and kinds bitvid uses
• relays.md — relay compatibility and COUNT fallbacks
• testing.md — QA checklist + test vectors