Files
bitvid/docs
thePR0M3TH3ANandClaude Opus 4.8 8f39b2c479 feat(signer): surface an actionable notice when the signer goes unresponsive
A raw window.nostr probe in the user's browser (getPublicKey → nip04.encrypt
→ nip04.decrypt, bypassing ALL of bitvid) HUNG forever, with the extension's
own console showing `ObjectMultiplex - orphaned data for "background-liveness"`
+ `malformed chunk` + listener-leak warnings. That is the NIP-07 extension's
content-script ↔ background-service-worker channel being dead (classic MV3
worker death) — an extension/environment failure, not a bitvid bug. No client
change can force an unresponsive signer to answer; the fix is to reload/unlock
the extension.

What bitvid CAN do is stop failing silently. Add js/utils/signerHealthNotice.js:
after a few consecutive list-decrypt timeouts while the signer reports itself
present, emit ONE rate-limited, actionable user notice ("your signer isn't
responding to decryption — unlock/reload the extension and refresh") instead of
the silent 15-minute retry loop. Reset on any decrypt success so a transient
blip doesn't warn. Wired into blocks, hashtags, and subscriptions.

Also documents the definitive root-cause + all resilience increments in
KNOWN_BUGS #0. Test: tests/signer-health-notice.test.mjs (threshold, rate-limit,
success-reset). Full unit suite green.

Co-Authored-By: Claude Opus 4.8 <[email protected]>
2026-06-16 14:18:46 -04:00
..
2026-01-23 02:27:15 -05:00
2026-02-05 19:31:19 -05:00
2025-11-03 20:48:06 -05:00
2026-01-23 02:27:15 -05:00
2026-01-30 09:13:54 -05:00

Documentation Index

Welcome to the bitvid documentation. This directory contains detailed architectural guides, API references, and system overviews.

Core Systems

Nostr Protocol

Moderation & Safety

  • Moderation Service: How content moderation, reporting, and admin lists function.
  • Logging Strategy: Guidelines for using devLogger vs userLogger and production logging policies.

Design & UI

Operations

For more details on contributing, please see CONTRIBUTING.md.