#1337 - WebSub (PubSubHubbub) support
| Identifier | #1337 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | WebSub (PubSubHubbub) support |
| Status | Open |
| Tags |
Type: Mobile (custom) Type: Performance (custom) |
| Handling member | Deleted |
| Addon | syndication |
| Description | Implement support for WebSub (previously named PubSubHubbub) in addition to the existing RSS cloud support. |
| Steps to reproduce | |
| Additional information | Google are preferring PubSubHubbub. I had an exchange with a Google engineer on Techcrunch.com when PubSubHubbub was released, and they had not even heard of the official RSS cloud feature when they were designing PubSubHubbub - now it's political, as Google are pushing their own standard (grr...). |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".


Comments
"The specific mechanism for the publisher to inform the hub is left unspecified. For example, some existing public hubs [1] [2] [3] ask publishers to send a POST request with the keys hub.mode="publish" and hub.url=(the URL of the resource that was updated)." [https://www.w3.org/TR/websub/#publishing]
I'm not sure exactly why we'd want to implement 3rd party companies personal standards in Composr. It seems a bit bizarre to me, handing off control to the private companies who are choosing to implement hubs - the W3C should have properly specified it.
The whole advantage of WebSub over RSS Cloud is that the heavy lifting is off-loaded to the hub. So we can't realistically implement a hub ourselves as that defeats the whole point. But if we implement for some company's specific hub protocol, we are not being open.
The only reason I could see to implement private companies WebSub ping protocols is if our implementation of RSS Cloud really was being overwhelmed by lots of users requesting to be pinged about updated resources at the same time. This has never been a problem, and I don't expect it to be - as there are only a handful of feed readers out there that are going to implement subscription to an RSS Cloud server (Feedly?) - and few people use RSS anyway.