I have come across this article
about CSS-related vulnerabilities in email clients. It's quite shocking what you can do with CSS if you render arbitrary CSS from a third party. RSS readers have challenges similar to email clients: they both embed HTML from untrusted third parties. Not all readers support CSS though. Some go the easy route and just filter it out. Inoreader is a popular reader with CSS support, while Feedly does not support it. My project Downread supports CSS, so this is something that concerns me as well.
While RSS readers typically show feeds the user trusts, you can't always rely on that. Especially when users are adding comment feeds or aggregators. So filtering HTML is one of the crucial but more difficult parts of writing an RSS reader. On the one hand, you want to allow as much HTML as possible to allow rendering the feed as well as possible. On the other hand, RSS readers can't allow everything. Not only for security reasons, but also to prevent feeds from breaking the RSS reader's UI, especially when the reader is HTML-based and renders posts in its own DOM tree.
Unfortunately, RSS and other syndication formats (Atom, JSON Feed) do not make any attempt to specify an HTML subset to be used in feeds. As readers can't allow full HTML, this will inevitably lead to incompatibilities between readers. I believe this is something to be addressed, and I will come back to in a future post here.
But the main point I was going to make here was: be careful. If you are the user of an RSS reader, make sure you get one you can trust, because it's a tool you process untrusted data with. And as an author of RSS tools, be aware of the fallacies that come with rendering untrusted HTML.
There is this old argument about whether Atom is really superior to RSS. It comes back every once in a while, and also this weekend on Hacker News
. Like so often, the central point is the format and encoding of texts and dates. Here, the main example is the <title> element. This is my comment on the original article:
I agree that Atom is easier to use and better defined in some ways. But why on earth would you want to put unrestricted HTML in the title in the first place? How is a reader supposed to handle that? It's just a weird thing to allow.
In practice, the differences between the syndication formats don't really matter. Today even less than when they were created, as a solution for most of the differences is just a prompt away.
it doesn't allow bad things like HTML in titles (which I guarantee >50% of all implementations can't handle correctly)
JSON Feed allows feeds to have a <favicon> and a (square!) <icon>, which is a very practical thing for readers. You can use the <favicon> in lists of feeds, and the <icon> to present a single feed. Atom has a small square icon and a <logo> which is supposed to use a 2:1 aspect ratio. 2:1 is completely useless. No site has a logo in 2:1. It's also useless for most full-name logos, like 'New York Times'. (RSS is, of course, even worse; it doesn't even recommend an aspect ratio, practically guaranteeing that RSS readers can look bad.)
You can see that JSON Feed has been designed from a feed consumer's point of view: what does an RSS reader need to make a feed look good? While Atom and RSS have been written from an abstract publisher's point of view, making everything possible and allowing maximum flexibility. Especially RSS, which has shown its flexibility in becoming the de facto format for podcasts. And both Atom and RSS are really old, written at a time when it probably wasn't clear how RSS would eventually be used.
In the end, no matter which format a feed uses, users won't notice any difference (as long as publishers are smart enough to use square images!). So any feed is a win, no matter whether RSS, Atom, or JSON Feed.
There was a time, back in the 2000s and early 2010s, when RSS was nearly mainstream. All enthusiasts knew it, and most used it. Websites prominently featured their RSS buttons. Web browsers had built-in RSS support. And Google Reader made RSS accessible to regular users. But what happened?
RSS Logo
The End of Google Reader
Google shut down Reader, removed RSS support from Chrome, and RSS became hard to use for most users. Most likely, Google Reader was an expensive distraction for Google that didn't generate any revenue. Back then, social networks were all the rage, and Google wanted a share of the pie with Google+. For a while, it looked like social media could replace RSS readers, and user numbers were declining as people spent more time on social networks. Of course, that was at a time when social networks weren't really monetized either and didn't have nearly the volume of advertisements they have today.
Without Google, not only did the biggest brand name supporting RSS disappear. The remaining RSS readers were mostly designed for enthusiasts. Capable, but packed with complicated features mostly relevant to power users, full of jargon and with less user-friendly design. Like many others, I switched to Feedly back then, as it was the most similar available reader and they made it easy to migrate. But today, it looks like Feedly has mostly pulled out of the market and pivoted to the more profitable market of threat intelligence. Feedly can still be used as an RSS reader, but go to their website, and you see a threat intelligence tool, not a reader.
RSS Readers from a Beginner's Perspective
Let's say you've heard about RSS readers being a great invention, and you Google it. This is what Google returns:
Your first hit is rssview.app. You open it, and this is what you see: Technically, it's an interesting reader that allows you to read a feed without logging in. But for a new user, that's just incomprehensible mumbo jumbo with no easy way of understanding how this can work. Just want to read the New York Times? Not a chance!
Current RSS Readers Are for Power Users
Thankfully, Google's AI Overview lists some popular RSS readers. The first one is Inoreader. Arguably the most powerful reader on the market, and with a generous free plan. But I'm not sure this landing page, and especially the screenshot, appeals to non-technical first-time users of RSS.
Without any doubt, Inoreader is a great product for power users. But it's not an attractive product for first-time users.
NewsBlur is similar. It's more like a power tool, designed for maximum functionality, not for usability.
NetNewsWire's simple interface is closer to a feed reader that is easy to use. Without any doubt, it is simple and clean. It just doesn't make it easy for the user. There is no catalog of feeds, no help managing feeds, and no web version.
The Content Publisher Dilemma
However, RSS readers are far from the only challenge for RSS. The sad truth is, it's hard to make money from offering an RSS feed, especially for ad-financed sites. While RSS feeds can generate additional traffic for articles, at the same time, every user who does not visit the site's homepage is a user who won't see the site's ads.
The case is even more difficult for publishers who publish not just summaries or headlines, but whole articles through RSS. These publishers will see zero revenue from RSS. At best, they can place some affiliate links.
In the end, it's also a blessing that the number of RSS users is not that significant, as the possible loss in ad revenue stays low that way. If most users used RSS, there would be much more scrutiny about the cost and benefit of RSS feeds, and we might end up with fewer RSS feeds than today.
How Can RSS Get (Back) to Mainstream Users?
I believe there are two things missing for RSS to really thrive.
ubiquitous RSS readers: just look at podcast apps. They come with phones; they are bundled in services like Spotify; and they are easy to use. Everybody is just a click or two away from listening to a podcast. Reading an RSS feed is far more complicated. Either RSS readers must be as widespread as podcast apps, or there needs to be a well-known RSS reader that everybody can easily find.
a business model for feeds: this may be the bigger issue. Many feeds just offer summaries, so they can create revenue with users on their own website. Some sites offer full-text feeds for subscribers (like The Verge does), but this is rare. An easy system to allow publishers to get paid when a user reads their feed would go a long way in motivating them to promote their RSS feeds.
Until we have at least one of those things, ideally both, RSS readers will stay a niche product.