Social-relay 1.3.0 released
Social-relay is a server application to act as a relay for public content using the #Diaspora protocol. The idea is simple. Social nodes utilizing this protocol expose their subscription preferences, nodes send content to the relays and the relays push the content they receive onwards to subscribing nodes as per their subscriptions. Subscriptions can be a list of hashtags or "all". Read more about the relay system here.
Want to hook on to the relay system as a node admin? Diaspora pods can enable outbound and/or inbound relay settings in their
diaspora.yml configuration file. #Friendica and #Hubzilla nodes can do the same (please check respective server documentation for how to do this).
Recently, since Diaspora version 0.6 was released, the relay system (composed of 3 relays at the moment) has seen a big increase in traffic, going to an average ~2500 public posts per day pushed around to ~75 subscribing servers. This meant that some performance related changes were needed.
Version 1.3.0 brings the following performance related changes:
- Since more than one worker is now needed to process the traffic, SQLite doesn't cut it as a database. With this release, the options are now PostgreSQL and MySQL/MariaDB, with support for SQLite removed.
- To make it easier to run a relay, the need to separately run scheduled jobs and RQ workers has been removed. A Circus configuration file has been provided which will run 1 scheduled jobs process and X amount of workers. This allows easily scaling to any amount of workers necessary (at ~35MB RAM each you can afford some!) to handle increasing relay traffic.
See full changelog: https://github.com/jaywink/social-relay/releases/tag/1.3.0