4 Commits

Include renames

Author	SHA1	Message	Date
thepraandClaude Opus 5.5	796f06acf4	The inbox answers once it has verified, and processes from the job queue ... InboxService is split the way the roadmap lays out Federation/Inbox: - InboxReceiver reads and verifies the request exactly as before, runs the checks that need no fetch (the activity id's origin, a Follow of a missing or local-only actor, an Undo of someone else's activity, an embedded object attributed to someone else), queues a ProcessInbox job and answers 202. The job's dedupe key is the activity id, so a peer that delivers the same activity twice is processed once. - InboxProcessor (two at a time, eight attempts) loads the verified actor and hands the activity to the handler for its type. - Handlers/{Follow,Undo,Create,Delete,Update}Handler are the old methods, unchanged except that they no longer produce status codes; the JSON helpers live in Objects/ActivityJson and the group membership helpers in Inbox/ForeignMembers. A slow fetch of an object or a remote actor now delays the job, not the sender's HTTP request. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012CzABvBkbcFqoHdmi8b9WB	2026-10-01 11:12:34 +02:00
thepraandClaude Opus 5.5	d80cd42a0c	Rate limits on accounts and inboxes, a database dump before every deploy ... - Sign-up, login, the invitation flows and password recovery allow ten requests a minute per client address; the inboxes give each sending origin (the keyId's) a bucket of 300 that refills at 300 a minute, and answer 429 beyond it, which peers retry. - deploy.yml dumps the PrivaPub database to /var/backups before it stops the service (the last seven are kept), and after the swap checks that Swagger answers 404 and that the shared inbox answers junk with 400 and an unsigned activity with 401. - ActivityPubClient and PostBoost, never used, are gone. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012CzABvBkbcFqoHdmi8b9WB	2026-10-01 11:02:21 +02:00
thepraandClaude Opus 5.5	2eb2a63f1e	Conversations are keyed by who is in them, and circles stay home ... S8: a direct message joins a conversation only when its participants are exactly that conversation's members, found through a new DmGroup.ParticipantsKey (a hash of the sorted members). A remote context no longer decides anything: it let anyone who knew a conversation's context post into it, and joining by context while dropping a participant would have shown a reply to someone it was not addressed to. A context is kept only when it is on the author's origin. Sending a DM to the same people again reuses their conversation instead of opening a new one. S9: Group.Kind is Circle or Community. A circle is not a federated actor: its actor, collections, WebFinger and inbox answer 404, a remote Follow is refused, and posts in it are IsLocalOnly - never delivered, never in an outbox, never served. Communities keep today's behaviour until P4. Migration _003 makes every existing group a circle, marks their posts local-only and backfills the conversation keys. End-to-end inbox tests sign real deliveries from a fake peer: a context injection, a forged activity id, a note attributed to someone else, a cross-origin object, a bad signature, junk bodies and a Follow of a circle. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012CzABvBkbcFqoHdmi8b9WB	2026-10-01 10:57:01 +02:00
thepraandClaude Opus 5.5	034b792801	Move the federation code under Federation/, namespaces only ... Services/Federation and Controllers/ServerToServer become Federation/{Actors,Signing,Inbox,Outbox,Rendering,Controllers}, the first step of the roadmap's layout. No type, route or behaviour changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012CzABvBkbcFqoHdmi8b9WB	2026-10-01 10:39:41 +02:00