Reid 'arrdem' McKenzie
||2 weeks ago|
|docs||7 months ago|
|installation||4 years ago|
|relay||2 weeks ago|
|.gitignore||3 years ago|
|Dockerfile||7 months ago|
|LICENSE||4 years ago|
|README.md||2 weeks ago|
|docker.sh||7 months ago|
|pyproject.toml||1 year ago|
|relay.yaml.example||7 months ago|
|requirements.txt||7 months ago|
|setup.cfg||4 months ago|
|setup.py||1 year ago|
A generic LitePub message relay.
This relay is forked from https://git.pleroma.social/pleroma/relay, and patched to a working state.
What is a relay?
A relay is a webserver implementing ActivityPub/LitePub. Normally when posting content on an ActivityPub server, that content is only listed publicly on the feed of the hosting server. Relays provide a way for ActivityPub servers to announce posts to a wider audience and receive posts from elsewhere.
What is this program?
The relay itself is a webserver providing two major components.
- A hardcoded webfinger implementation for resolving the user
- A message relay, which will perform a stateless relay of new activity to connected nodes
The relay offers three moderation capabilities:
- An explicit allowlist mode restricting connected nodes
- A denylist mode restricting connected nodes by name
- A denylist mode restricting connected nodes by self-identified server software
Normally, you would direct your LitePub instance software to follow the LitePub actor found on the relay. In Pleroma this would be something like:
$ MIX_ENV=prod mix relay_follow https://your.relay.hostname/actor
On Mastodon the process is similar, in
Administration > Relays > Add New Relay one would list the relay's URL
ActivityRelay is copyrighted, but free software, licensed under the terms of the GNU Affero General Public License version 3 (AGPLv3) license.
You can find a copy of it in this package as the