diumFile-sharing UX should default to P2P (browser-to-browser), with relay fallback. The transfer interface should disclose which path was used: 'Sent peer-to-peer' or 'Sent via relay (server-touched).' Most workflows accept the default; sensitive workflows require it.
Local-first software is no longer a fringe architectural opinion. Linear, Figma, Replicache, Yjs and Automerge made it the default mental model for any client-heavy app where latency and ownership matter. Community software is the next workload to make the shift, and Why Your File-Sharing UX Should Default to 'Never Touched Our Servers' sits exactly inside that shift. The essay that follows is for the engineers and platform leads who already know latency-first UX is correct and want the schema, the conflict-resolution rule, and the operational tooling to make it real.
Why default matters
If the default is server-relayed, every file the community ever shared is on your server. Backups have it. Logs may reference it. Subpoenas can request it. If the default is P2P, the file existed only between sender and recipient; the server never had a copy.
The disclosure UX
On send-success, the UI shows which path was used. 'Sent peer-to-peer' for direct WebRTC. 'Sent via relay (server retained metadata only)' for TURN fallback. 'Sent via encrypted upload (expires in 24h)' for offline-recipient fallback. Transparency builds trust.
Who this matters for
- Healthcare networks sharing case notes
- Legal communities exchanging redacted briefs
- Financial advisor groups sharing confidential portfolios
- Abuse-survivor support exchanging sensitive resources
- Whistleblower-adjacent communities
Why most platforms don't do this
Building P2P + signaling + TURN + fallback is a non-trivial engineering investment. Most community platforms cut the corner and ship server-relayed only. The platforms that invest in P2P win the buyers who shop on data exhaust.
Why local-first matters for community workloads now
Three forces aligned in 2025-2026. Browser storage quotas finally became reliable enough to lean on. WebRTC interop reached the point where browser-to-browser transfers are a real product affordance, not a demo. Privacy regulation tightened to the point where "we never had your file on our server" became a procurement asset, not a footnote. Why Your File-Sharing UX Should Default to 'Never Touched Our Servers' sits in the intersection. The platforms that ship the architecture now win the buyers who shop on data exhaust over the next two renewal cycles.
The engineering frame
Treat the user's device as the first source of truth for the user's own state. Drafts, read marks, local notes, the cached feed: all of it lives in IndexedDB and renders before any network round trip. The server becomes a peer that helps reconcile, not the primary store. This inversion sounds extreme until you build it; once shipped it makes everything else cheaper, including the privacy story, the offline story, and the operator-sovereignty narrative for self-host buyers.
Last-write-wins reconciliation with per-record version stamps handles 99.7% of community workloads at one-tenth the cost of CRDTs. Reach for CRDTs only when you have a specific co-edited record (shared agendas, co-authored Broadcasts) that demands them. Resist the temptation to ML-ify or distributed-systems-ify the architecture before the workload asks for it; the simpler model wins on debuggability and ships in months instead of quarters.
A pattern from the field
We see the same pattern across the operators we work with. The teams who treat Why Your File-Sharing UX Should Default to 'Never Touched Our Servers' as an upstream design decision: encoded in the platform's defaults, surfaced in the operator dashboard, and audited as a standing line item in the quarterly review: see the downstream metrics move within 60-90 days. The teams who treat it as a setting to revisit later watch their dashboards flatline through three quarters before they reopen the question. The difference is rarely talent or budget; it is the willingness to make the decision once, document it, and let the rest of the platform compose around it. The cost of revisiting later is paid in the metric you would have moved if you had not been firefighting the symptom.
Failure modes we have shipped and recovered from
- Treating IndexedDB as a trust boundary and storing JWTs there. XSS becomes a one-step compromise; it is not subtle.
- Skipping schema versioning on day one and trying to retrofit migrations after the first production incident.
- Letting the sync queue grow unbounded when the server is unreachable, then watching browsers OOM in the field.
- Ignoring the storage quota until 80% triggers an eviction storm during peak event traffic.
- Shipping a reconcile rule that is "mostly" deterministic and discovering the non-determinism only when two users argue about whose version of a draft is correct.
What to ship this sprint
Audit your slowest write path. Time it from button-press to UI-confirm. If it is over 500ms, you have the easiest and highest-impact local-first fix available. Invert the order: optimistic local update first, network round-trip second, sync queue handles the reconciliation. The same write that took 1.2 seconds will land under 100ms perceived. Members who used to hesitate before posting will post; the contribution rate will move within the same week. That single inversion is the gateway drug to the rest of the architecture.
The takeaway
Local-first is the architectural shift that converted Linear and Figma into the products their categories now compare themselves to. The community-software category has not made the shift yet, broadly. The platforms that make it next compete on a UX that pure-fetch competitors structurally cannot match, on a privacy story the regulatory environment is about to require, and on a sovereignty narrative that opens enterprise procurement. Why Your File-Sharing UX Should Default to 'Never Touched Our Servers' is one of the load-bearing pieces. Ship it correctly once and the rest of the architecture follows.