Author here. What many people claiming "RSS is dead" for the last 20+ years mean is that RSS-as-feed (for written content) is not mainstream, and that's somewhat true. Most podcast listeners don't have a proper RSS reader apart from their podcast app. Also, big platforms removing existing RSS support is often taken as another sign of RSS dying.
What's interesting is that this particular post had been posted by someone on HN before I've shared it anywhere. So it got through RSS right onto the HN front page. This is what I meant with "thriving, especially among tech users".
My experience as someone who's in the tech sphere but writes not only about tech is that RSS is all but dead. Not sure if i'm an outlier in this but the % of requests in my server logs coming from RSS is very high.
Like you I tried to figure out how many of those are actual users to have a sense of how many people still use it and the numbers still don't make any sense to me.
That said, what do you think is the benefit of styling an RSS page? The point of the rss is to be consumed via an RSS reader so I don't see the benefit of having styles on a page like that. But maybe there's something I'm missing here.
Yes, styled RSS feeds don't provide any value when consumed by RSS readers. But when I visit a blog and click an RSS feed link for the first time, it's nice to have a short preview of the existing posts without having to parse XML visually. The main benefit I see is however to educate people who don't know what RSS is. Imagine a person clicks "RSS feed" and all they see is some strange-looking file. On my feed [0], there is a big banner with a short explanation and a link to learn more about the technology.
Yeah that's probably useful. Btw your recent blog posts are sorted in a weird order according to the dates.
Also, and not sure why this is happening, I have the Reeder extension installed on safari and it usually automatically prompts me to open an rss link in the app but it doesn't happen in your case.
I can't even use the button in the browser toolbar to open the feed in the app directly. The only way for me to add it is to manually copy paste the url.
The posts are sorted by date, newest being at the top. I haven't posted much in 2022 and 2023, so maybe "Jun → Dec → Mar → Dec" looks confusing if you miss the according year?
Regarding Reeder, I've included the feed in the markup, so I'm not sure what is going on. I will definitely have a look, thanks for the finding!
Oh, you mean in the feed preview. Yeah, they're sorted by publish date but I only display the last update date. I see that it's quite confusing, I'll fix that. Thanks!
The author is pointing out that someone who clicks an RSS/Atom link and gets a page of gibberish is not going to understand all that XML, and they will likely just go back to the site confused.
Instead, you can have a readable page with a message like the one in the post: "This is an RSS feed. Subscribe by copying the URL from the address bar into your newsreader. Visit About Feeds to learn more and get started. It’s free."
I can see some value in redirecting people towards a page that explain what RSS is. Not entire sure about the first part about letting people know how to subscribe to an rss feed because people who decide to use an RSS reader probably know already how to use it since it's a somewhat technical tool but still, probably doesn't hurt to provide extra info.
I work in podcasts and not with written content RSS feeds, but at least in the podcasting world, I would take traffic from RSS endpoints with a grain of salt - a lot of reader clients like to request updates very frequently, and it's not unreasonable at all that a user that consumes your content primarily through RSS makes one or even two order of magnitudes more requests than someone who visits your site.
The parent might be referring to my other post [0]. Some RSS readers - at least Inoreader, Feedbin and Feedly - send the actual subscriber count as part of their HTTP request. Which is nice to get at least a minimum number of total subscriptions. Not sure if popular podcasting apps do that as well, though.
I wrote about my findings here[0] and honestly I don’t even know what to make of those numbers. RSS stats are stupidly hard to track, especially if you only rely on server logs which is what I do.
> ... tech is that RSS is all but dead. Not sure if i'm an outlier in this but the % of requests in my server logs coming from RSS is very high.
I'm not sure which you meant here—is your perspective that RSS is thriving (judging from your traffic) or nearly dead?
There are two very similar English idioms that have opposite meanings: "all but dead" means basically dead, "anything but dead" means not even a little bit dead.
> Most podcast listeners don't have a proper RSS reader apart from their podcast app.
Sure, but I would assume that "RSS is dead" isn't so much about consumer awareness of RSS, but rather about the technology being invisibly supported and used in the infrastructure they make use of (through podcast clients et al) such that content producers still care about publishing through RSS.
Like, if I said "TLS1.0 is dead", I wouldn't be referring to greenfield projects not using it any more; but rather to the fact that the browsers and libraries that invisibly use it (and nothing newer) are themselves not being used by anyone any more — so nobody on the content-delivery end has to think about supporting TLS1.0 clients any more, and can drop any code that was supporting that.
But that's definitely not the case with RSS. There are still many important systems that depend on consuming RSS feeds. So there are people who still need to support RSS. So it's alive.
> RSS is alive and well and mainstream with podcasts.
Spotify (and other big players) are doing their best to end this.
As many as one in four podcast listeners currently use spotify to listen. The growing number of spotify-only podcasts are not available via RSS. Most of the listened-to podcasts may also be available as RSS, but the listeners wouldn't know either way. Spotify's goal is to be the chokepoint for podcasts.
Spotify isn't the only one. The way to make money on podcasts is by being the distribution platform, and by locking people in with non-open standards.
Spotify still uses RSS as a distribution channel from your host to Spotify - you supply a RSS feed through Spotify for Podcasters or another ingestion service. They don't allow adding by RSS feed for end users, but that's not all that rare among players.
But there are also spotify-only podcasts, which are not distributed to spotify like that, are not available via RSS or any other method but a spotify client.
This is an intentional business move by spotify. They are attempting to change the podcast landscape.
Although googling for recent sources, it looks like there's been some pushback and slight retreat -- looks like their plan wasn't exactly working. Yet. I'm sure they haven't given up yet:
> After the cancellations and resulting layoffs, members of the Gimlet union blamed Spotify’s exclusivity strategy for disappointing numbers. Although the shows were not behind a paywall (free subscribers to Spotify could access them, as well), they did not enjoy the kind of wide distribution that the shows did before the acquisition. It’s not like they don’t have a big platform — according to a study by Cumulus and Signal Hill, Spotify is tied with YouTube as the most-used podcasting platform. But even then, it only has about one-fifth of the market.
Spotify and Apple are both acting anti-competitively in different ways. Spotify has their exclusives (which from the looks of it seem to be largely not a huge success outside of Joe Rogan and something they appear to not be focusing on as much), but Apple is very anti-competitive when it comes to direct podcast monetization like support and subscriptions where Spotify has taken a very open approach.
If your player wasn't spotify, now you know why! Spotify bought them and took them spotify-exclusive, in part of an attempt to gain control of podcasting landscape.
And if you are typical, apparently the gimlet staff were right to be worried that this hurt their numbers!
Not so sure about podcasts. At least where I am from (Italy) a great deal of podcasts are either Spotify exclusives, or consumed mostly through Spotify, or bundled in some producer-specific app (e.g. the state-owned radio does this, and doesn't provide feeds).
The vast majority of podcast content is distributed via RSS. In fact if its not distributed via RSS, no one is listening. It’s so important its even advertised as part of Spotify’s podcasting platform.[0]
Of course Spotify has incentive to prioritize you listening in their app, but they can still put ads into the audio feed so it doesn’t matter as much to them. And your state-owned radio is absolutely limiting their audience by not using the accepted standards for podcast content.
I would not be surprised if Spotify themselves get the audio from the source via RSS/Atom.
No doubt the podcast creator may have to create an account and tell Spotify manually (and also on Apple, Google, etc), but once the feed is in their system the creators/producers just need to update things in one place and all the 'distribution points' get the new episode.
RSS is alive and well and mainstream with podcasts.
Also: how many folks use RSS(-as-protocol) and how many use Atom (RSS-as-feed)?