mirrors/buzzrelay
1
0
Fork 0
mirror of https://github.com/astro/buzzrelay.git synced 2024-11-21 11:41:00 +00:00
Code Issues Projects Releases Packages Wiki Activity
Source to relay.fedi.buzz: relay the streaming API of Mastodon instances
103 commits 1 branch 0 tags 2 MiB
Rust 83.3%
Nix 8%
HTML 5.9%
CSS 1.9%
JavaScript 0.9%
Find a file
Astro 52cfe9c493 relay: shorten worker queue length from 1024 to 8
2023-10-09 02:25:25 +02:00
src relay: shorten worker queue length from 1024 to 8 2023-10-09 02:25:25 +02:00
static static/index.html: update tagline 2023-09-29 01:41:47 +02:00
.gitignore README: init 2023-01-11 19:41:48 +01:00
Cargo.lock fetch, send: use httpdate for formatting Date: header 2023-10-07 03:25:43 +02:00
Cargo.toml fetch, send: use httpdate for formatting Date: header 2023-10-07 03:25:43 +02:00
config.yaml config.yaml: document the API access_token required for Mastodon 4.2.0 2023-08-10 01:37:50 +02:00
flake.lock flake.lock: Update 2023-09-28 21:28:55 +02:00
flake.nix flake.nix: fix meta.description 2023-05-14 23:33:22 +02:00
LICENSE LICENSE: add 2023-01-11 19:39:39 +01:00
nixos-module.nix nixos-module: add option logLevel 2023-06-24 01:28:12 +02:00
README.md README: init 2023-01-11 19:41:48 +01:00

README.md

buzzrelay

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 relay.fedi.buzz.

Setup

Build

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.

Database

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

The program will create its schema on start.

Ethics

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 fedi.buzz serves the firehose feed through the streaming API, too.

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