Federation:Relays names relays by their actor (or inbox) address; the instance actor follows Public at each, as Mastodon subscribes, a minute after start and every six hours (asked again a day after no answer or a refusal, undone when a relay is no longer named). What an accepted relay passes on comes to the federated timeline and nobody's home: a public post it forwards (Activity-Relay), read again from its origin like any forwarded post, and a post it announces (aode-relay), kept as its author's and never as the relay's boost. Nothing of a persona's is sent to a relay; sending public posts there waits for the owner. The pasture gains both relays (peers/relay.sh, peers/aoderelay.sh) and scenarios/relay.sh, 13 checks. The village backlog is clean: 2574 checks pass, one known gap (Misskey's). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LsXgEaXee4GCU1hwYgPJXw
711 B
711 B
Interop backlog
Generated by tools/pasture/town.sh backlog --write from village-20261005-220341 on 2026-10-05. Do not edit by hand: fix the cause, or record a known gap in tools/pasture/town/gaps.json, and generate it again.
Checks: 2574 pass, 0 fail, 1 known gaps, 0 known gaps now passing.
New failures
None.
Known gaps still failing
- G-0005 (peer, upstream): Misskey keeps a post's renote count when a remote Undo{Announce} deletes the renote, so an undone boost still counts. 1 checks. Code:
misskey-dev/misskey packages/backend/src/core/NoteDeleteService.ts: only repliesCount is decremented on delete.
Known gaps now passing (close them)
None.
Scenario failures
None.