I've been using XSLT on RSS feeds forever now. It's a pretty awesome way to make it browser-accessible now that no browsers want to natively handle feeds. If you want to self-host an XSL for a feed it can be tricky serving the feed with the right Content-Type because some browsers want to throw feeds over to an external app even though they can display it themselves. My favorite part is styling makes XML serve its or…
Totally breaks some RSS readers that render the page before processing.
Show HN: RSS.Beauty – Make Your RSS Beautiful
11–20 of 24 posts
Re: Show HN: RSS.Beauty – Make Your RSS Beautiful
#12The use of Tailwind feels rather bloated to me. Seems a big part of why it is 22KB for RSS.xsl. Not that you necessarily need to code golf an XSLT file to be as small as possible, but it just contributes to my disregard for Tailwind itself as a source of bloat as another example from the wild where Tailwind seems verbose and baroque.
Re: Show HN: RSS.Beauty – Make Your RSS Beautiful
#13Tried to use on mobile firefox, but seems to be doing something very CPU intensive, doesn't respond for ~10s then the tab crashes
Re: Show HN: RSS.Beauty – Make Your RSS Beautiful
#14Re: Show HN: RSS.Beauty – Make Your RSS Beautiful
#15I've been using XSLT on RSS feeds forever now. It's a pretty awesome way to make it browser-accessible now that no browsers want to natively handle feeds. If you want to self-host an XSL for a feed it can be tricky serving the feed with the right Content-Type because some browsers want to throw feeds over to an external app even though they can display it themselves. My favorite part is styling makes XML serve its or…
Re: Show HN: RSS.Beauty – Make Your RSS Beautiful
#16Re: Show HN: RSS.Beauty – Make Your RSS Beautiful
#17Re: Show HN: RSS.Beauty – Make Your RSS Beautiful
#18I've been using XSLT on RSS feeds forever now. It's a pretty awesome way to make it browser-accessible now that no browsers want to natively handle feeds. If you want to self-host an XSL for a feed it can be tricky serving the feed with the right Content-Type because some browsers want to throw feeds over to an external app even though they can display it themselves. My favorite part is styling makes XML serve its or…
However, the compatibility differences among various browsers are significant, and the adaptation difficulty is also very high.
Typically browser engines that don't support an XML specification version will do the proscribed thing and ignore it. So some old Series 60 WAP browser (were you to find such a thing today) would ignore the XSL stylesheet and display the raw XML or hand it to the registered handler for the content type.
The world went bonkers supporting XML on every computing platform under the Sun for nearly a decade.
Re: Show HN: RSS.Beauty – Make Your RSS Beautiful
#19Earlier quoted context omitted.
We sincerely apologize for the inconvenience caused.
:) That's not necessary, but it would be interesting to know what trips Firefox up like that.
All of this during the Holiday Season too!
Re: Show HN: RSS.Beauty – Make Your RSS Beautiful
#20Earlier quoted context omitted.
:) That's not necessary, but it would be interesting to know what trips Firefox up like that.
Hi, I am part of the Mozilla community. Mozilla devs read through comments and saw an issue with Firefox. They filed https://bugzilla.mozilla.org/show_bug.cgi?id=1939643 to identify why it doesnt work only in Firefox. Turns out other browsers do not follow the spec, and the underlying libraries that the page uses used workarounds to make it work in Chrome, but that broke Firefox. We filed https://github.com/tsparticl…