The relay server: an update on our open release

What we're publishing

The initial open release of the PluralLog Relay Server will include the full API spec, the server codebase, and a basic admin dashboard. It'll ship as a Docker image (or, more likely a pair) — PostgreSQL or SQLite, S3-compatible or local filesystem — with minimal configuration. We currently have a working version of both the relay and dashboard that fits these requirements, both being implemented as separate services, however I am currently reviewing this implementation to see if any problems pop out.

What's taking time

Mostly honesty. There are known gaps in the current protocol that we want to address before we publish. Specifically, there's not yet sufficient protection against a relay operator acting in bad faith in certain ways. We don't want to hand people something they'll build communities around and then have to tell them it needs a breaking change. There are a couple cryptographic features that our lead developer was originally targeting, but recent shifts in the availability of apps like Octocon and SimplyPlural have moved our target deadline significantly. With this in mind, we shifted our targets so that when we implement a stronger model (exact details on forward direction at release) we can implement those changes with minimum friction and possibly even no changes to the app clients.

We're working through it. The cryptographic foundation is (mostly) solid; it's the protocol layer we're still refining.

What to expect when it ships

• A single Docker image, minimal config
• Full API documentation matching the implemented client protocol
• Rate limiting and abuse prevention built in
• No telemetry, no phone-home, no license server
• SQLite support for small self-hosted instances
• Example relay expansion adding admin features, admin dashboard

If you're interested in running a community relay and want to stay in the loop, get in touch.