Comment by data_base
6 days ago
I use RSS Style[1] to make the RSS and Atom feeds for my blog human readable. It styles the xml feeds and inserts a message at the top about the feed being meant for news readers, not people. Thus technically making it "safe" for less tech savvy people.
What about Google killing XSLT? https://developer.chrome.com/docs/web-platform/deprecating-x...
Browsers really should have embraced XSLT rather that abandoned it. Now we're stuck trying yet again to reinvent solutions already handled by REST [1].
[1] https://tonysull.co/articles/mcp-is-the-wrong-answer/
XSLT is the solution domain specialists and philosophers. Abandoning it is the vote of the market and market interests, the wisdom of crowds at work. This is the era of scale not expertise, enjoy the fruits.
4 replies →
RSS.style is my site. I'm currently testing a JavaScript-based workaround that should look just like the current XSLT version. It will not require the XSLT polyfill (which sort-of works, but seems fragile).
One bonus is that it will be easier to customize for people that know JavaScript but don't know XSLT (which is a lot of people, including me).
You'll still need to add a line to the feed source code.
> message at the top about the feed being meant for news readers
There's no real reason to take this position. A styled XML document is just another page.
For example, if you're using a static site generator where the front page of your /blog.html shows the most recent N posts, and the /blog/feed.xml shows the most recent N posts, then...?
A reason to add that explanation to a styled RSS feed is to teach visitors what newsreaders are.
A message explaining what feeds and feedreaders are would suffice for that.