lichenblankie/tinyweb-forum
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

readme: document trust circle design

Browse source
This commit is contained in:
blankie 2026-06-17 19:11:25 +00:00
parent 3a26a726a4
commit 3120e38cb8
1 changed files with 15 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

17
README.md
View file

@ -36,12 +36,23 @@ Enable it on TinyWeb's `/style` page under "Forum".
- Threads are auto-pruned after 30 days (configurable, or set to 0 to keep everything) - Threads are auto-pruned after 30 days (configurable, or set to 0 to keep everything)
- Moderation is local: block authors, mute threads, keyword filters, and gossip block lists with peers (auto-block after 3 peer reports) - Moderation is local: block authors, mute threads, keyword filters, and gossip block lists with peers (auto-block after 3 peer reports)
### Trust circle
Content exchange is gated by a trust graph derived from your TinyWeb subscriptions:
- Only peers you subscribe to (with forum enabled) are trusted sources of content
- Content from trusted peers propagates transitively: you see posts from their trusted peers, and theirs, and so on — no hop limit
- No open registration: a new identity has zero connections and zero reach. No bot can join without a human vouching for them
- This is structural: spam is not a moderation problem, it's a graph problem
Trust is seeded from TinyWeb's subscription page — each subscription has a "forum: on/off" toggle. When enabled, that peer's forum content (and their transitive trust network) enters your view.
## Moderation ## Moderation
All moderation is local — it controls what you see: All moderation is local — it controls what you see:
- **Block author** — hides all content from that identity - **Block author** — hides all content from that identity and cascades: the blocked peer's downstream trust network (peers they vouched for) is also removed from your view. If a downstream peer has an alternate trust path from another source you trust, they survive the cascade.
- **Auto-block** — when 3+ of your peers have blocked the same identity, it blocks for you too - **Auto-block** — when 3+ of your peers have blocked the same identity, it blocks for you too (with cascade)
- **Mute thread** — hides a thread from the listing - **Mute thread** — hides a thread from the listing
- **Keyword filters** — hides threads matching keywords - **Keyword filters** — hides threads matching keywords
- **Instance sync** — choose which peers to sync with; unsync at any time - **Instance sync** — choose which peers to sync with; unsync at any time
@ -71,6 +82,7 @@ All moderation is local — it controls what you see:
- Retractions are voluntary — peers can ignore them - Retractions are voluntary — peers can ignore them
- Block gossip can be gamed (requires collusion by 3+ peers on Reticulum) - Block gossip can be gamed (requires collusion by 3+ peers on Reticulum)
- Threads prune after 30 days by default - Threads prune after 30 days by default
- The trust circle replaces open discovery: you can't find interesting strangers through topic blooms alone. Discovery is through the existing subscription graph — you find people your trusted peers already know.
- Best-effort maintenance - Best-effort maintenance
## Security ## Security
@ -79,3 +91,4 @@ All moderation is local — it controls what you see:
- **Retractions are voluntary** — Retracting a thread or post sends a signal to peers, but any peer can ignore it. "Retract" is a polite request, not a guaranteed delete. - **Retractions are voluntary** — Retracting a thread or post sends a signal to peers, but any peer can ignore it. "Retract" is a polite request, not a guaranteed delete.
- **Block gossip can be gamed** — Auto-block triggers after 3 peer reports. On Reticulum this requires 3+ real instances to collude, which is impractical at mesh scale, but is not cryptographically enforced. - **Block gossip can be gamed** — Auto-block triggers after 3 peer reports. On Reticulum this requires 3+ real instances to collude, which is impractical at mesh scale, but is not cryptographically enforced.
- **No rate limiting** — Forum POST endpoints have no throttling. Low risk since the HTTP port is localhost-only by default. - **No rate limiting** — Forum POST endpoints have no throttling. Low risk since the HTTP port is localhost-only by default.
- **Trust circle** — Spam resistance is structural (no open entry), not procedural. The weakest point is social engineering: a trusted human adding a bad actor. Mitigated by cascade removal on block — blocking a peer removes their entire downstream trust network from your view.