You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actor, inbox, outbox and followers; follow/accept; publishing a Note from a
drive table, with delivery through the ontola/atomic-server#1719 queue. A view shows Inbox and
Outbox tables and delivery health. Evidence: a follow and reply round trip
with one Mastodon and one GoToSocial instance.
From the design in #108 (docs/design/server-plugin-routes.md, #88). Filed by the atomic-plugins oversight session.
Per Michiel's decision, the server-protocol plugins are owned by the Codex PRs; this is covered by #163 (Fediverse / ActivityPub). The atomic-plugins oversight session won't implement it separately.
#217 merged: the Fediverse plugin publishes a public ActivityPub actor. It uses WebFinger and NodeInfo; Follows are auto-accepted with a signed Accept; posts made through the outbox are delivered, signed, to followers' shared inboxes; replies are stored. The real-host e2e passes at pin candidate16 against a local ActivityPub peer; it hasn't been tried against real Mastodon. The catalog entry is enabled: false. The limits are in integrations/fediverse/README.md.
A real Mastodon 4.7.3 now completes follow → Accept → a published Note in the home timeline → a reply stored in the drive → unfollow with the plugin. This runs in the opt-in integrations/fediverse/e2e/mastodon.spec.ts (FEDIVERSE_MASTODON_E2E=1, Docker, loopback only, invented accounts) and passed at pin a12b74a on 2026-10-02 (PR #282).
One plugin fix: the actor's FEP-2c59 webfinger handle, needed because Mastodon drops the port when it checks a handle. The wire details are in the README, "Against a real Mastodon".
GoToSocial isn't done. 0.22.1 refuses unsigned actor GETs with 401, and the host fetches keys unsigned. Delivery to per-account inboxes is also refused, by the https://*/inbox operation. Both are host changes, so under the freeze they're issue drafts for Joep (on #227). This issue stays open for GoToSocial, and for a run on a real public domain, which needs Michiel's OK.
Activity
michielbdejong commentedon Sep 25, 2026
Per Michiel's decision, the server-protocol plugins are owned by the Codex PRs; this is covered by #163 (Fediverse / ActivityPub). The atomic-plugins oversight session won't implement it separately.
michielbdejong commentedon Sep 29, 2026
#217 merged: the Fediverse plugin publishes a public ActivityPub actor. It uses WebFinger and NodeInfo; Follows are auto-accepted with a signed Accept; posts made through the outbox are delivered, signed, to followers' shared inboxes; replies are stored. The real-host e2e passes at pin candidate16 against a local ActivityPub peer; it hasn't been tried against real Mastodon. The catalog entry is
enabled: false. The limits are inintegrations/fediverse/README.md.michielbdejong commentedon Oct 2, 2026
A real Mastodon 4.7.3 now completes follow → Accept → a published Note in the home timeline → a reply stored in the drive → unfollow with the plugin. This runs in the opt-in
integrations/fediverse/e2e/mastodon.spec.ts(FEDIVERSE_MASTODON_E2E=1, Docker, loopback only, invented accounts) and passed at pin a12b74a on 2026-10-02 (PR #282).One plugin fix: the actor's FEP-2c59
webfingerhandle, needed because Mastodon drops the port when it checks a handle. The wire details are in the README, "Against a real Mastodon".GoToSocial isn't done. 0.22.1 refuses unsigned actor GETs with 401, and the host fetches keys unsigned. Delivery to per-account inboxes is also refused, by the
https://*/inboxoperation. Both are host changes, so under the freeze they're issue drafts for Joep (on #227). This issue stays open for GoToSocial, and for a run on a real public domain, which needs Michiel's OK.Generated by Claude Code
Merge pull request #282 from ontola/claude/fediverse-real-peer
Merge pull request #286 from ontola/claude/fediverse-akkoma