ChatGPT: Was rssCloud superseded by WebSub?

No file, test, or entry point is named in this issue, and it does not request a code or documentation change. Clarify the intended project change and identify the relevant RSS/WebSub documentation location; done should be a documented, agreed resolution.

Short answer: No — WebSub did not supersede rssCloud.

Different technical philosophy

• rssCloud assumes a decentralized RSS network where each feed URL is the identity, and publishing = updating the feed.
• WebSub assumes a hub-based architecture with a broker intermediary between publisher and subscriber.

These are fundamentally different models and not successive versions of the same protocol.

Different adoption histories

• rssCloud is widely adopted quietly. It works in real-world RSS ecosystems and powers real-time feed updates across existing infrastructure.
• WebSub got W3C attention but limited adoption. It never reached critical mass among RSS readers or publishers.

Persistence of infrastructure

If WebSub actually replaced rssCloud:

• WordPress would have dropped rssCloud — it didn’t.
• Feed readers would have switched — they didn’t.
• Real-time RSS distribution would have moved — it didn’t.

Simplicity vs abstraction

• rssCloud: notify all subscribers directly.
• WebSub: publisher → hub → subscriber

WebSub introduces more moving parts and centralized intermediaries, which is a poorer fit for the decentralized ethos of RSS.

Practical reality

People sometimes claim WebSub replaced rssCloud because it sounds like a neat narrative:

• new official spec → old protocol obsolete

But in practice:

• rssCloud stayed in production
• WebSub never became the default
• the ecosystem didn’t migrate

Conclusion: rssCloud was not superseded by WebSub. They are different approaches that co-exist, and rssCloud remains actively used in the real world.