Source to relay the streaming API of Mastodon instances
Go to file
2024-07-09 15:23:07 +02:00
.github/workflows .github/workflows/build: install dependencies 2024-03-27 23:11:09 +01:00
src fetch, send: run signature in spawn_blocking 2024-06-07 02:22:26 +02:00
static static: repair HTML 2023-10-27 01:53:45 +02:00
.gitignore README: init 2023-01-11 19:41:48 +01:00
Cargo.lock Cargo.lock: update 2024-06-16 00:42:11 +02:00
Cargo.toml Cargo: update dependencies 2024-06-07 02:14:59 +02:00
config.yaml add RedisConfig.password_file 2023-10-12 22:09:43 +02:00
flake.lock flake.lock: Update 2024-06-16 00:35:10 +02:00
flake.nix flake.nix: add cargo-outdated to devShell 2024-06-16 00:42:20 +02:00 tweaked wording for proxy section 2024-04-11 02:30:31 -05:00
LICENSE LICENSE: add 2023-01-11 19:39:39 +01:00
nixos-module.nix nixos-module: make package overridable 2024-07-09 15:23:07 +02:00 README: link Ubuntu howto post 2024-04-09 23:37:45 +02:00


A follow-only ActivityPub relay that connects to Mastodon's Streaming API.

You don't need to run this yourself, just use the instance at


See also: Notes on an setting up a fediverse relay with FediBuzz on an Ubuntu server.


NixOS/Flakes users are in luck: not only does this build, it also comes with a NixOS module!

Anyone else installs a Rust toolchain to build with:

cargo build --release

Generate signing keypair

ActivityPub messages are signed using RSA keys. Generate a keypair first:

openssl genrsa -out private-key.pem 4096
openssl rsa -in private-key.pem -pubout -out public-key.pem

Let your config.yaml point there.


Create a PostgreSQL database and user, set them in your config.yaml.

The program will create its schema on start.


Should everyone connect to the streaming API of the big popular Mastodon instances?

Once these connections become a problem, they may become disallowed, resulting in problems for everyone. That's why serves the firehose feed through the streaming API, too.

You can let this service use as listed in the default config.yaml.