cloud_hub is an update notification hub server that implements two APIs that are typically used to enable near-realtime updates for subscribers of RSS and Atom feeds.

• For RSS 2.0 publishers, the server exposes the compliant "http-rest" and "https-rest" protocols of the RSSCloud API. The "xml-rpc" protocol is not implemented at present, but could be added if there is interest.

• For Atom publishers, the server exposes the WebSub Hub API.

The two APIs share much in common, and are used to distribute notifications of live changes from various publishers.

The RssCloud API exposes two HTTP POST URLs, per the spec:

• The /rsscloud/pleaseNotify URL is used by an interested subscriber to request realtime updates to a given resource.

• The /rsscloud/ping URL is used by a publisher to inform the hub of an update to a resource. If any subscribers have requested updates for the resource, they are notified by an HTTP POST callback.

If you are a subscriber, please see the RSSCloud API docs or Dave Winer's RSS Cloud Walkthrough article for more information on the www-form-urlencoded parameters that should be sent to these URLs, and for how the hub server will request validation and send notification callbacks.

If you the publisher of an RSS 2.0 feed, you can add a <cloud> child element to the <channel> element in your feed, with these attributes:

• protocol set to "http-rest" or "https-rest" depending on the endpoint URL for your cloud_hub deployment.
• domain set to the host name of the endpoint URL for your cloud_hub deployment.
• port set to the TCP port of the endpoint URL of your cloud_hub deployment.
• path set to "/rsscloud/pleaseNotify"
• registerProcedure set to "" (XML-RPC is not implemented)

See the RSS 2.0 Specification for more information about the <cloud> element.

Then whenever you update your feed (the "resource"), send a HTTP POST request to the /rsscloud/ping URL on the cloud_hub server with one www-form-urlencoded parameter:

• url, with a value set to the the URL that the cloud_hub server will use to fetch the updated resource.

After the post to /rsscloud/ping, any subscribers who are subcribed to the URL will be notified via an asynchronous callback.

The WebSub Hub API exposes one HTTP POST URL, at /hub.

• When sent a www-form-urlencoded parameter "hub.mode" with a value of either "subscribe" or "unsubscribe", this URL is used by subscribers to request realtime updates or to cancel previously established subscriptions, respectively.

• After a publisher updates a resource, it sends a "hub.mode" parameter with a value of "publish" to the /hub URL. If any subscribers have requested updates for the resource, they receive the updated contents via an asynchronous HTTP POST callback.

If you are a subscriber, please see Section 5 of the WebSub Hub specification for information on the parameters that must be sent in the POST body to the /hub URL.

If you are the publisher of an Atom feed, your feed should include at least two <link> elements as children of the <feed> element.

• A <link> with a rel attribute having the value "self". The href attribute should be the URL that the WebSub Hub server will use to fetch resource content when it has been updated.

• A <link> with a rel attribute having the value "hub". The href attribute should be the URL of your cloud_hub deployment (with the path component of the URL being "/hub").

Then whenever you update your feed (the "resource"), send a HTTP POST request to the /hub URL on the cloud_hub server with two www-form-urlencoded parameters:

• hub.mode, with a value of "publish".

• hub.topic, with a value set to the the URL that the cloud_hub server will use to fetch the updated resource.

The /status URL uses Phoenix LiveView to provide a dashboard of the hub's activity. At present, this is exposed publicly.

See the issues list at https://github.com/pzingg/cloud_hub/issues, and feel free to note bugs.

You can setup your own development / production environment of cloud_hub as with any normal Elixir / Phoenix development.

• Clone this repository.
• Install dependencies with mix deps.get
• Create and migrate your database with mix ecto.setup
• Start Phoenix endpoint with mix phx.server or inside IEx with iex -S mix phx.server

Now you can visit localhost:4000 from your browser.

Ready to run in production? Please check our deployment guides.

This repository is forked from the original WebSubHub repository by Luke Strickland. Work to extend the server to support RSSCloud, and other changes made for future compatibility with the Mastodon-compatible Akkoma Fediverse microblogging server are by Peter Zingg.

1. Fork it!
2. Create your feature branch (git checkout -b feature/my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin feature/my-new-feature)
5. Create new Pull Request

The project includes a comprehensive test suite, so you should be encouraged to run tests as frequently as possible.

mix test

If you need help with anything, please feel free to open a GitHub issue at the original WebSub Hub-only repository or at this combined WebSub Hub and RSS Cloud repository.

cloud_hub is licensed under the MIT License.