6f240828cfecf923b39816bf0e095be4b030043e
The fan-out put every post in its author's home, located ones too, while the Mastodon API looks past located posts everywhere else. In the author's home a located post showed as public (the mapper has no word for it) and every action on it answered 404: decePub's end-to-end runs, which write one from Milano for the globe, found it there. The fan-out now gives a located post no home, no stream and no notification, and the home timeline passes over the entries left from before. A located post is read through /clientapi/post/nearby and deleted through /clientapi/post/delete. NearbyTests checks it has no TimelineEntry; the suite passes (881). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LsXgEaXee4GCU1hwYgPJXw
Everything on, phase 1: geolocation fetches itself, the deploy signs in as @thepra, the crawler is on, sign-up by invitation
PrivaPub
A self-hosted ActivityPub server in C# (.NET 10, MongoDB) where one private login owns several unlinkable public personas. It federates with Mastodon, GoToSocial, Pleroma/Akkoma, Misskey and Lemmy.
- Live: https://privapub.thepra.dev
- Client: decePubClient, https://decepub.thepra.dev
- Architecture, conventions and deploy: CLAUDE.md
- Decisions and the plan to full ActivityPub interop: docs/ROADMAP.md
dotnet build PrivaPub.sln -c Release
Languages
C#
79.6%
Shell
14.2%
Python
5.8%
HTML
0.2%
Dockerfile
0.2%