Social-Relay version 1.2.0
New version of the public content #relay
server software. This version brings support for passing through also #Diaspora
protocol Retraction messages (ie deletions of content). This is important since otherwise a post later deleted that the relay originally delivered would not be delivered. Issues exist in #Diaspora
issue trackers to get retractions to be sent to the relays.https://github.com/jaywink/social-relay/releases/tag/1.2.0
Next for the relay system I intend to separate the relay system documentation to it's own repository, since it's not really a part of Social-Relay which is just the server implementing it. Would love to get some opinions on various subjects there then, regarding how to proceed with things like decentralizing the relays and getting rid of the reliance on the-federation.info as a way to bootstrap lists of nodes. Preferably opinions from project admins since the decision on how to decentralize the relays has to be done the way the projects are fine implementing it.
Ping @Davìd M
and @Jeremy Pope
. Additionally please note the change in the requirement files. I simplified them a bit, changelog has details.
[1.2.0] - 2016-10-25
- Expose NodeInfo to allow registering relays to pod lists. Unfortunately, NodeInfo schema doesn't contain the relay software key so this NodeInfo document cannot be validated by consumers.
- Network calls now use a custom user agent
Social-Relay/<version> - https://github.com/jaywink/social-relay. Thanks @bmanojlovic for the patch.
- Relay also Diaspora retraction and photo entities. The former follows the same way like and comment entities are relayed, ie the targets are the same as where the status_message or photo were relayed. photo follows same rules as status_message entities, ie according to subscriber wishes.
- Replaced custom payload sending with the new helper from federation. This will not try to deliver to http targets at all. This means nodes that are not using https will not get deliveries. Really, these days, there is no reason to run a public website with http.
- Removed suggestion to use pip-tools and convert requirements files to standard Python project requirements files. Didn't dig the workflow after all. To install dev dependencies use requirements/development.txt. For production, use requirements/production.txt, which also contains uWSGI. If you don't deploy using uWSGI, you can just use requirements/requirements.txt.
social-relay - Public post relay for the Diaspora federated social network protocol