ChatGPT: Was rssCloud superseded by WebSub?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- networking
Research direction
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.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- HTML
- Stars
- 134
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from scripting/Scripting-News
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
scripting/Scripting-News#353 · 6 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
scripting/Scripting-News#332 · 25 comments · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
scripting/Scripting-News#362 ·
-
Matt is moved aside Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
scripting/Scripting-News#361 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
scripting/Scripting-News#360 · 1 comment · 1 reaction ·
All issues in scripting/Scripting-News
Similar issues
-
kind/bug Ubuntu 24
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
kubernetes-sigs/kubespray#13532 ·
-
language/en needs-triage sig/network
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
kubernetes/website#57642 · 1 comment ·
-
app.loanspq.com OpenN: AdGuard DNS P3: Medium T: Incorrect Blocking
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AdguardTeam/AdguardFilters#242018 ·
-
[adam] AdamNet network read doesn't cap to MAX_ADAM_PACKET_LEN, overflows client receive buffers Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
FujiNetWIFI/fujinet-firmware#1649 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
daeuniverse/dae#1116 · 1 comment ·