"It’s wonderfully idealistic, but the reality of RSS is that it lacks the features required by nearly every actor in the modern content ecosystem"
> for something as simple as syndication and distribution, HTML already has an overwhelming advantage over any nascent formats
> It would make subscribing to a site easier, since one wouldn't have to find the URL of the RSS feed. The URL of the weblog itself would be what you wanted. How nice.
werd.io/2015/signed-feeds-pubsub-a-simple-verb-protocol-a-publisher-and
werd.io/2015/scene-100-years-into-the-future-an-apocalyptic-wasteland-shouts
werd.io/2015/one-man-surviving-the-apocalypse-in-his-radiation-proof-exoskeleton-simply
werd.io/2015/in-the-distance-app-city-with-its-gleaming-towers-and
werd.io/2015/the-masters-of-app-city-carefully-snip-and-prune-the
werd.io/2015/on-one-side-coders-fighting-for-the-user-hands-bloodied
With all of the debate lately between RSSCloud versus PubSubHubbub, we wanted to hear from a developer who could actually tell us which one might be better and why. The following guest post is written by Josh Fraser, the co-founder of EventVue, who is an active contributor to PubSubHubbub in his free time. He has contributed several client libraries for PubSubHubbub including a WordPress plugin. Guess which side of the debate he falls on.
twitter.com/davewiner/status/565208821250162688
twitter.com/davewiner/status/565209513125752832
twitter.com/julien51/status/565209990764707840
twitter.com/kevinmarks/status/565211528807186434
twitter.com/julien51/status/565212335045083136
twitter.com/kevinmarks/status/565213155995828225
twitter.com/kylewm2/status/565215955010084864
twitter.com/davewiner/status/565216227111735296
twitter.com/kylewm2/status/565216497086107648
twitter.com/davewiner/status/565217122398527489
twitter.com/davewiner/status/565217242053627904
twitter.com/davewiner/status/565217346454032386
twitter.com/davewiner/status/565217471062634496
twitter.com/davewiner/status/565217564532686848
twitter.com/kylewm2/status/565219809751597057
twitter.com/kylewm2/status/565220603175505921
twitter.com/davewiner/status/565220719098077185
twitter.com/davewiner/status/565220817018294275
twitter.com/davewiner/status/565220946697793536
twitter.com/kylewm2/status/565221013399425024
twitter.com/davewiner/status/565221063521738752
twitter.com/davewiner/status/565221171734781952
twitter.com/davewiner/status/565221288277721088
twitter.com/davewiner/status/565221373162057730
twitter.com/davewiner/status/565221715933138944
twitter.com/kylewm2/status/565222869395722240
twitter.com/davewiner/status/565223988298022912
twitter.com/davewiner/status/565224119210631168
twitter.com/davewiner/status/565224767725531136
twitter.com/davewiner/status/565224891130335233
twitter.com/kylewm2/status/565225174048313344
twitter.com/davewiner/status/565227746851561472
twitter.com/aaronpk/status/565228346141716481
twitter.com/davewiner/status/565233359564312576
twitter.com/davewiner/status/565233450035453952
aaronparecki.com/replies/2015/02/10/6/
twitter.com/davewiner/status/565238642453798912
but I suspect the hardest part is the client app for readers, which works in a way analogous to an RSS reader or email client, but would have to support a new format and would be optimized for clean reading and subsequent discovery, rather than the three-pane model which has dominated those apps for the last decade or two
RSS won not because of its great design, but because there was a significant amount of valuable content flowing through it. Formats and protocols by themselves are meaningless. That's what I say about specs. Show me content I can get at through the protocol, and I'll say something.