diumThe Community Platform as a Local-First App
IndexedDB schema, last-write-wins reconciliation, sync queues with backoff, and why your forum belongs on the user's device first.
Local-first and P2P
Engineering notes on browser storage, sync, peer-to-peer file sharing and the trade-offs of keeping community data close to the member.
Browser-to-Browser Document Sharing: WebRTC DataChannel, SHA-256, TURN Fallback
Product page disguised as a tutorial. Files never touch our servers; integrity verified at the receiver.
Why Your File-Sharing UX Should Default to 'Never Touched Our Servers'
Privacy-positioning post. The default should be P2P; the fallback should be relayed; the operator should disclose which.
The 5-Step Bootstrap Flow: From asq.php to a Hydrated SPA in <800ms
Architecture deep-dive. PHP shell → bootstrap JSON → remote JS/CSS → IndexedDB hydrate → API session exchange.
Why IndexedDB Is a Cache, Not a Trust Boundary, and the Bug That Taught Us
Treating IndexedDB-stored credentials as authoritative is XSS-equivalent compromise. Auth must use short-lived signed tokens.
Versioned Remote Bundles + Kill-Switch: How We Ship JS Without Bricking 200 Communities
Remote-loaded SPAs require version pinning, integrity metadata, kill-switch blocklist, percentage canaries, and per-tenant pinning.
Optimistic UI for Community Posting: the 4 Conflict Cases Nobody Handles
Stale auth, removed parent, rate limit, content rejection. The four cases optimistic UIs need to handle without losing the user's content.
A Signed Bootstrap Envelope: the 1-Paragraph Fix for Half of Community Auth Bugs
Sign the bootstrap payload with a short TTL, audience restriction, and nonce. Server exchanges it for a runtime session.
CSP, SRI, and Nonce-Based Scripts for a Remotely-Loaded Community SPA
Remote-shell SPAs require CSP allowlists for shell origin + tenant API, SRI for pinned bundle versions, and nonce'd inline scripts for theming.
The 6-Table Schema Behind Every Modern Wave-Based Community
Spec-derived. Six tables hold the entire forum + lobby + sponsor stack.
The Notification Taxonomy: 4 Urgency Tiers and the Wake-Up Rule
Ambient (in-app) / digest (email) / interactive (push with action) / wake-up (call/SMS). Four tiers with explicit thresholds.
Digest Emails That Don't Get Muted: the 7-Block Layout
Digest emails open at 38% when structured as: who's online → 1 question for you → 3 conversations near you → 1 office hour → 1 sponsor offer → unsubscribe-by-topic.
Quiet Hours, Timezone-Aware Scheduling, and the 1-Tap RSVP From Email
Notifications respect 3 axes: quiet hours, timezone, urgency tier. One-tap RSVP from email lifts attendance by 19%.
Animated Explainer: 'How a P2P File Transfer Actually Works in Your Browser'
Lottie + diagrams: signaling server pairs peers, ICE finds path, DTLS encrypts, DataChannel chunks 16KB at a time.
'The Forum Architecture Map' Poster (24x36, Downloadable)
Engineering eye-candy: a wave platform stack: PHP shell → bootstrap JSON → SPA → API → WS/SSE → IndexedDB cache → P2P signaling.