What we lost – a paean, perhaps, to RSS
mattmower.com
mattmower.com
I never really got into it properly (though I paid for and used feedbin for a while) not least because not everything supports it. Its main attraction to me is as being the one place I can go for everything, and if it isn't that, then.. meh, it's just another thing to check, and I gradually stopped.
Not that I don't intend to go back (as much as I intend to do a lot of things..) - it just needs more setup to be useful to me, email subscriptions to RSS for example, or perhaps even the other way around, have an email folder full of subs with rss forwarded there too.
Other things that annoyed me were latex not rendering, and the RSS article being just a tiny stub, or title only, linking to the real deal.
There's actually quite a few powerful services to do this. I made a service called http://feedsub.com to do this a couple years ago. I'd also recommend http://mailbrew.com which has a nice digest format.
I think there's a lot of value in RSS as an underlying data layer for the web, and I think it's criminally underused on the consumption side nowadays.
For example, I'd very much like to see blogrings make a comeback, and there's probably room for a website community driven entirely by mailing lists and one of these RSS-to-email tools.
Feedbin does this, FWIW. You mentioned you had used Feedbin before, maybe they introduced the feature after you left? It's super useful, and justifies the cost of the subscription all by itself for me. All my newsletter subscriptions go into my Feedbin feed, and my email inbox stays nice and clean (and my real email address stays nice and private).
I've personally just been using Feedly's free tier, and it works fine. Every now and then they find a new way to say "hey, what if you paid for Feedly," but it hasn't bothered me too much.
They don't advertise it, but it's there - I presume because whatever CMS they use supports it (WordPress, etc).
It's not popular, and I do worry that what you state will come to pass, but I remain thankful that nearly a decade later, it hasn't yet.
But, the article seems to be describing something else.
Today k-Collector would not be possible. That alternative future where everyone started blogging and putting their content in RSS2.0 feeds that we could analyse to connect those conversations did not happen.
I honestly didn't understand the article. I gathered that he created some kind of tool that aggregated blog posts based on their tags and created an RSS feed out of that, maybe like delic.io.us did? But isn't that already being done by the RSS readers? So, I still think I don't understand the article.
Looks like TFA’s tool was a way to surface these.
Which is to say: It is a problem to be solved with communication and coordination tools kinda like this (but much lower urgency)
https://www.kalzumeus.com/2014/04/09/what-heartbleed-can-tea...
As described, k-Collector seems to be solving a subset of the problem space that delic.io.us did. kConnect presents feeds of different blogs grouped by tag, while delic.io.us did the same, but for all websites, not just blog posts. What am I missing?
It sounds like a really interesting experiment, is why I'm so interested. Are you sure it can't be revived?
Thankfully many RSS readers have an equivalent to a browser's Reader Mode that fetches the page and strips all the crap out of it. It's not perfect by any stretch, but it beats getting blasted by cookie popups, newsletter signups, and autoplaying video.
Personally I don't even parse the <content>, I just have headlines sorted by <pubDate> that open the pages in the browser.
In 2003/4 which is the period I was writing about there was no Facebook or Twitter and online advertising was not the business it is now. Although publishing via RSS was still relatively new and not well adopted it seemed like a viable way of plugging content together.
Now so much content is in silo's. There are no usable feeds from anyone who cares about advertising because they don't want you to have their content, they want to capture you.
That's what I am getting at. Not whether you can still read some sites that continue to support RSS in a reader.
It's also worth remembering that they are a relatively new phenomenon developed in response to the snooping. There was a long period where companies like Facebook had it all their own way. And this is the period in which the damage was mostly done.
It will surprise you how often people just do it. Its a fun thing to implement, 5-20 min and you have results that require little to no further attention, upgrades or maintenance.
What is dead, or at least like Arthur, waiting for the right moment to come back is the idea of RSS as a system for connecting content streams together and building higher order services on top.
When too much thought & conversation is captured inside Facebook, Twitter, Slack and all these other services who depend upon owning you & your content, the RSS system cannot thrive.
I saw amazing possibilities arising out of individuals publishing their content, increasing use of micro-formats to add semantic information, and layering of services. That future didn't happen.
That's what I am sad about.
> What is dead, or at least like Arthur, waiting for the right moment to come back is the idea of RSS as a system for connecting content streams together and building higher order services on top.
The closest to it is the situation with the podcast ecosystem, which if I recall correctly depends heavily on RSS feeds to propagate podcasts’ playlists.
> When too much thought & conversation is captured inside Facebook, Twitter, Slack and all these other services who depend upon owning you & your content, the RSS system cannot thrive.
I agree that information capture by various social media is quite troubling. I am currently worried the most about all development-related discussion in many minor projects and communities (not only programming-related) switching over to Discord, of all things.
Despite this, I disagree with the assessment that it is a major bottleneck for the RSS ecosystem. I have never used Google Reader, so I don’t have any kind of before and after perspective, but in my humble opinion RSS is a standard that is in quite a good condition overall. Despite social medias’ walled garden approach and greater focus on instant messaging than blogging, I rarely stumble upon a website with content of episodic nature without any kind of RSS feed. The only significant exceptions are YouTube and Twitter.
> I saw amazing possibilities arising out of individuals publishing their content, […], and layering of services. That future didn't happen.
The thing you describe reminds me more of something akin to Mastodon and ActivityPub (albeit I never used any platform depending on it). From what I remember about ActivityPub was that it was designed from ground-up as both a protocol and an extendable system to plug into as a clear alternative to walled-garden design. From what I gather, RSS was never meant to be that.
How such a system based on RSS only would even look like?
> […] increasing use of micro-formats to add semantic information, […]
Isn’t it basically what JSON-LD, Microdata and RDFa do? With a bonus of not being tied to any walled garden (that I am aware of). Though I suppose having a way to use them in a more automatic way would be nice.
>Despite this, I disagree with the assessment that it is a major bottleneck for the RSS ecosystem. I have never used Google Reader, so I don’t have any kind of before and after perspective, but in my humble opinion RSS is a standard that is in quite a good condition overall. Despite social medias’ walled garden approach and greater focus on instant messaging than blogging, I rarely stumble upon a website with content of episodic nature without any kind of RSS feed. The only significant exceptions are YouTube and Twitter.
As I have mentioned in several other comments, there is nothing wrong with RSS2.0 the protocol (at least nothing that wasn't also wrong with it in 2003).
Without being funny about it, perspective is important.
In 2003/4 publishing via RSS was a nascent thing. Blogs did it, but blogging was still in it's infancy. Some corporations were starting to do it, and were being encouraged to share value through RSS feeds.
There were aggregators (we built one, but there were several) that were starting to show what you could do by bringing these disparate content streams together. We were also having a little susccess in persuading companies to encourage their employees at all levels to blog and to create internal aggregators.
But, over time, applications like Facebook, Twitter, Slack, Discord have taken the momentum. Facebook, to pick one example, has at present 2.85 billion active users, many of them posting content which is not available outside Facebook. Twitter had RSS feeds but discontinued them. (Additionally, many blogs which do provide RSS feeds only provide excerpts of the content intended to draw you to their website & adverts).
You can't aggregate this content. These systems are also closed over creating, you use the tools they provide or you don't play. Want to do an experiment with how you create Facebook content? You can't. Facebook/Twitter reserve that to themselves.
If you try and start a project now you will struggle with the fact that a huge % of your potential userbase are already in Facebook, Twitter, etc… and captured there.
So while RSS still works and, yes, my blog still has an RSS feed, and you can read it in your RSS reader of choice, this is not the same situation as it was back then. And the futures that seemed possible from there do not seem possible from here.
I don't know, perhaps it's only with the perspective of being there that this feels this way.
Sometimes I feel people who see RSS/ATOM as a dead thing stopped seeing the existence of RSS feeds in their circles and then proceed to proclaim it dead.
The RSS protocol works as well as it ever did. I'm not mourning the protocol. And yes there are sites that do publish feeds, some even full-feeds but many just excerpts.
What I am mourning is the future where people published for themselves and shared content via RSS. But companies that depend upon advertising are inimical to that future and they won (at least for now).
It's that future that I mourn for.
Things like the death of Google Reader and web browsers making it harder or even disabling subscriptions to websites via RSS were a huge deal. Allegedly all of that was because RSS lost momentum.
People like me had to resort to use things like Feedly, but frankly it is not the same. I for one dream about the resurgence of RSS and making the web again a little less corporation-in-the-middle.
I have never seen someone under about 20 using RSS (and probably 90% of that age group has never heard of it). They all live in chat apps and algorithmic feeds :(
I couldn't imagine my RSS reader displaying stories that it thinks I'd like (and not all, in chronological order). There's a reason I curate my feeds—I want to see the content in each of them!
As well as the fact that most of the time, the actual content of the article is less interesting than the discussion it starts in the comments. I imagine most people checking reddit or HN are not there to read a long post but instead looking to discuss various opinions in the comments which RSS does not support.
RSS is for the long tail of blogs that don't post very frequently, but when they do, its worth your while.
The ideal entry in my RSS feed is one that has new addition once per week or less. This way, I can follow a very wide array of people without getting overwhelmed, nor having to miss if their post don't make it to HN front.
That's why RSS is still important, and why RSS feeds should not be delivered via Email.
How do you find those?
These days there are few awesome lists or the like for curated, sorted and tagged personal blogs too. Its a great time to start with RSS.
It's possible that you're reading the wrong blogs.
Im under 19 , i use rss daily for a lot of things from reading blogs to sending alerts about new updates in services me and my friends host.
I wish more people would join us outside the walled gardens, but I also don't think these tools will die so long as there's people like us that are passionate about staying outside the walled gardens.
I just checked wikipedia and it is coming up on a decade since v3 was started and yet no major network supports it. And v3 was only the bare minimum required to modernize IRC and misses so many other important features people demand like inline images/files and a mobile friendly protocol.
Of course it will never be dead in the sense that literally no one uses it. Almost nothing ever dies that way.
NewsBlur and other RSS aggregation sites are still around, have nice UIs and are still doing just fine.
I've put this in other comments but, briefly, it's not the protocol RSS that has a problem. It's the RSS-enabled future that we imagined back in the early 00's that didn't happen. Those opportunities for connecting things together via content (esp. around the RSS micro-formats work that was going on) disappeared when content got swallowed by advserisers.
I agree and can't help but hope this RSS thing and blogs will make a come back!
Alas, most of my email archive from that period disappeared in the intervening years. I'd love to be reminded of what we were talking about.
m@t
The biggest difference to me about modern RSS is the unrealized potential and lack of imagination.
There were some efforts at making it a bit more successful around 2005 with the likes of Feedburner and ads, but eventually it was realized that walled gardens were easier than open standards.
If we had put one tenth as much effort and imagination into making RSS a way that you could get timely information from the web, in such a way that it was as common and no-brainer to people as email is, as we did for web ads, user tracking, and email spy pixels, I think the web would be a lot healthier today.
The web has its good and bad points, but the web is different from the net, and much of what drives the web is bad for the net.
There is also the <rating> element which is even more exotic. It supplies an advisory label for the content in a feed, formatted according to the specification for the Platform for Internet Content Selection (PICS).
You can even run your own rating platform.
The categories are for grouping things. A typical blog would have few of them and many entries in each. The tags are more chaotic. Its fine to have a single article with a tag. The domain attribute is for a web directory (I think?) And with the rating system you can give your own units to a property like how advanced, complex or RSS-ish an article is. (arrogance in nano-Dijkstra)
All of that combined make for the best science fiction story.
With so many new websites being created and so many old ones deleted a static file is not a good solution. If we assume you manage to share your OPML with just the right audience it is almost impossible for a new blog to find its way into this promotional formula. You might find it eventually but it wont show up in the OPML for everyone you've shared it with.
My personal client can do OPML but also loads flat feed lists from an url then keeps additional flat lists of feeds that seem broken or gone, lists of feeds that I assume are gone and lists of feeds I'm no longer interested in. Removing the dead feeds and adding new ones still [shamefully] involves periodic manual labor.
Its great that one can manually categorize feeds in OPML and that one can provide categories, tags and even a rating service in the feed it self but if the data is never shared anyplace else their is [almost] no point in doing so. As a result most feeds have none.
We have: Tags, categories, your own rating system, a shared or public rating service, OPML meta data and the one I forgot: The person (or entity) sharing the feed(s) with you is also meta data.
I have no idea how we can wrap all of those into one discovery medium but the idea sounds awesome to me.
Or, in the immortal words of Goodfellas, "Fuck you, pay me".
NextCloud has an RSS reader app. Thunderbird has a whole RSS subscriptions area. AntennaPod for podcasts. Those are just a few.
Can anyone recommend a really simple RSS setup for Linux?
I work in vim if that means anything in this context whatsoever (I honestly have no idea).
Thanks friend.
You could skim some of that, as the nextcloud/owncloud stuff is in section 4.7. Good luck!
RSS has been damaged by in-fighting among those who advocate for it
http://www.smashcompany.com/technology/rss-has-been-damaged-...