The owner's six decisions on what PrivaPub reveals: previews, blocks, authorship, views, bridging, reactions
Build / Build (push) Successful in 57s

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012CzABvBkbcFqoHdmi8b9WB
This commit is contained in:
thepraandClaude Opus 5.5 committed 2026-10-01 17:32:59 +02:00
1 parent 829eae3ccf
commit 4c94254502
3 files changed
+26 -2

No files matched your search

+10 -1
View File
@@ -723,7 +723,16 @@ circuit breaker sees, and which signature scheme worked.
## 6. Choices the privacy design has to make
These change what PrivaPub reveals, so they are the owner's calls, not implementation details:
These change what PrivaPub reveals, so they are the owner's calls, not implementation details. **All six were decided on
2026-10-01; the decisions are in `docs/ROADMAP.md`, "Owner decisions on what PrivaPub reveals".** In short:
1. pages are fetched by the server for public posts;
2. blocks federate;
3. website authorship stays off;
4. PeerTube views are never sent;
5. Bluesky bridging is per persona, with persona dates randomised;
6. a one-time notice before the first reaction or vote.
The options as they were laid out:
1. **Link previews.**
- Building a card from the object, or from FEP-8967 `preview` data, fetches nothing; we do that.