Since version 1.0, Elytra has supported the WebSub protocol, and as a natural consequence of it: Push Notifications.
The WebSub protocol enables Elytra to receive real-time notifications from websites and update the internal cache of latest articles from these websites.
I recently noticed some abnormalities in the WebSub log that runs every weekend. Quite a few websites:
- Use an old (outdated) version of the protocol via a plugin (WordPress’ PuSHPress plugin) or similar
- Use a custom implementation that does not follow the protocol outlined by the W3C Doc.
This caused several websites to advertise their WebSub Hubs but not respond correctly to the subscription requests. A notable exception was Medium.com. While the RSS Feed URL for these were correct, Medium used to respond with a “incorrect topic url” error which was easy to fix because they also responded back with the correct URL to use for that feed.
I have since automated the above process, so no further actions are required by publishers relying on such hubs. However, if you are using any other implementation and WebSub doesn’t seem to be working on your blog:
- Try a different plugin (if you’re using a plugin)
- Try a different hub (some plugins allow you to define the hubs you would like to use)
- If you have written a custom implementation, ensure it uses the latest standards defined in the WebSub protocol linked above.
If you still run in to any issues, please feel free to get in touch with me at email@example.com.
Another issue I noticed is duplicate blogs. A lot of people import their OPML files into Elytra and detecting duplicates is often tricky. The reason is simple, a single blog sometimes has multiple URLs pointing to the same feed. Now the obvious solution would be to check the title, but that doesn’t work either because larger websites have separate feeds based on topics.
So detecting duplicates is tricky.
Solving the Problem
Both of these issues can be solved in the upcoming dashboard I am working on for Publishers. I hope to create a hub for Publishers to use for a nominal cost as well as enable publishers to group Duplicate blogs and RSS feeds and point to the single source of truth by claiming ownership of these RSS Feeds.
I’ll be publishing a consultation draft as to which features should be paid and which should be free, but I know one thing for sure: duplicate feeds consolidation will definitely be free for everyone. It is good for Elytra, you and your readers and this shouldn’t be an expense for anyone involved.