Add LitePub relay implementation #471
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds a LitePub-compatible ActivityPub relay implementation to the
@fedify/relaypackage, complementing the existing Mastodon relay implementation.Related Issue
#359
Changes
the LitePub relay protocol
activities before forwarding
packages/relay/src/relay.test.ts:455-832 covering:
Benefits
LitePub-compatible fediverse software, which expects activities to be wrapped in
Announce rather than directly forwarded
better visibility across the fediverse
(MastodonRelay) and LitePub-style (LitePubRelay) relay implementations based on
their target ecosystem
it easy to switch between protocols
Checklist
Additional Notes
Key differences between LitePub and Mastodon relay protocols:
- LitePub wraps activities in Announce objects with relay as actor
- Mastodon forwards activities directly using ctx.forwardActivity()
The implementation follows the same subscription management and key pair handling
as MastodonRelay, ensuring consistent behavior for core relay functionality like
follower management and subscription approvals.