30 Sep 2026
Activity Relay 3.0.1 has been released to fix a couple bugs caused by invalid follower states blocking relay operation.
https://github.com/thystra/Activity-Relay/releases/tag/v3.0.1
Activity-Relay 3.0.1 is a focused reliability release for follower-state handling and relay fan-out.
Fixed
- Prevent stale mutual-follow responses from recreating incomplete Redis follower records.
- Validate follower state before persistence.
- Ignore malformed persisted follower records when loading relay state.
- Isolate invalid or unplannable delivery targets so one bad receiver cannot abort healthy fan-out.
- Keep queue reservations and remaining-delivery counts aligned with deliveries actually planned.
- Harden manual follower acceptance ordering.
- Update Forgejo container/release CI for Debian Trixie’s split Docker client packages.
No configuration or data migration is required.
The 3.0.1 candidate was production-tested on relay.argentwolf.org, including real WordPress fan-out to healthy Friendica and Mastodon receivers while an independently failing receiver continued through its isolated retry path.
Container: ghcr.io/thystra/activity-relay:3.0.1
See docs/releases/v3.0.1.md and CHANGELOG.md for complete details.
The attached files are the exact canonical artifacts produced and accepted by the Forgejo release workflow.
If you find this useful, please consider leaving a tip on my Ko-Fi – https://ko-fi.com/thewolfandtheraven
#activitypub #fediverse #friendica #mastodon #nodebb #relay #relays #relayserver