this post was submitted on 29 Mar 2026
338 points (97.7% liked)

Technology

83295 readers
5269 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
all 46 comments
sorted by: hot top controversial new old
[–] JensSpahnpasta@feddit.org 16 points 2 days ago

It's sad to see how browser manufacturers have been treating RSS for a while. Back in the day your Firefox would show you that a page has an RSS feed. You were able to click on it, see what was in there in human readable, not cryptic-XML style format, and you were able to subscribe to it. Then you had a nice little bookmark showing you everything this page had posted recently. RSS is a great technology and it really really sucks how Big Tech has tried to kill it.

[–] Feyd@programming.dev 122 points 3 days ago (2 children)

Chrome's team argues that because only about 0.02% of page loads use XSLT, it's not worth the maintenance burden.

Surely given the volume of browser usage, 0.02% is still a very substantial amount of usage. Lazy fucks

[–] Kushan@lemmy.world 101 points 3 days ago (2 children)

I'm not entirely sure what the "maintenance burden" even is on a tech that hasn't changed in decades.

[–] floofloof@lemmy.ca 41 points 3 days ago* (last edited 3 days ago) (1 children)

From the article:

Google says it's removing XSLT to address security vulnerabilities. The underlying library that processes XSLT in Chrome (libxslt) is an aging C/C++ codebase with known memory safety issues. Chrome's team argues that because only about 0.02% of page loads use XSLT, it's not worth the maintenance burden.

It's debatable whether Google, with all its resources, really needs to do this, especially given that 0.02% of all page loads is still quite a lot. But there are certainly times when it's better to just delete seldom-used old code from your project to lower the maintenance burden and reduce the surface area for attacks.

Big tech has been straining the libxml2 dev who recently got annoyed with them. Instead of helping maintain the libraries they ship on billions of computers, Google is trying to reduce there use.

https://socket.dev/blog/libxml2-maintainer-ends-embargoed-vulnerability-reports

[–] cecilkorik@piefed.ca 16 points 3 days ago (1 children)

0.02% of page loads is honestly way more than I would've expected. The fact that they would look at that number and see an excuse to remove a feature like this is honestly a gigantic red flag for the way these browsers are being developed. Granted, it's not that surprising if you've been paying attention to the embrace-extend-extinguish march of web technologies towards a walled garden controlled by tech giants, but this is part of the writing on the wall, folks.

RSS is enabled by default on every WordPress install. That's a big part of it.

[–] pirate2377@lemmy.zip 29 points 3 days ago (1 children)

Wait, browsers still had RSS support? I thought that was deprecated a decade ago. I've been using dedicated apps for them

[–] clay_pidgin@sh.itjust.works 13 points 3 days ago

Vivaldi does. I assume there are chrome and Firefox plugins too.

[–] bjoern_tantau@swg-empire.de 47 points 3 days ago (1 children)

Xslt has nothing to do with RSS being available or not.

[–] confuser@lemmy.zip 25 points 3 days ago (1 children)

It seems to have to do with how it looks formatting wise and not about availability or not, that is what is being meant.

[–] bjoern_tantau@swg-empire.de 32 points 3 days ago (3 children)

That's just for those few websites that use their RSS feed as their content source. If they want to keep doing that they can just get a JavaScript library that provides XSLT functionality. The feed itself is untouched.

[–] 73QjabParc34Vebq@piefed.blahaj.zone 18 points 3 days ago (2 children)

"Yay more JavaScript" said nobody

[–] bjoern_tantau@swg-empire.de 8 points 3 days ago

It's really hard to decide whether XSLT or JavaScript is worse. On the one hand XSLT wasn't cobbled together in a weekend. On the other it requires you to write XML and its "arrays" start at 1.

[–] Papierkorb@feddit.org 3 points 3 days ago

Would be easy to render the XSLT in the server. Could be cached nicely as well.

[–] _wizard@lemmy.world 3 points 3 days ago (1 children)

So things like newsbreak who ingest a sites feed then display?

[–] Serinus@lemmy.world 11 points 3 days ago

Should be fine. They don't have to use a browser to retrieve that feed.

[–] confuser@lemmy.zip 2 points 3 days ago

Yep which is why the purpose of this post

[–] HeyThisIsntTheYMCA@lemmy.world 20 points 3 days ago* (last edited 3 days ago) (4 children)

i browsed the web via RSS for a while. Maybe it's time to get back to that. at least for some food blogs or something. anyone got a good rss reader?

[–] Matth@sh.itjust.works 7 points 3 days ago

Feeder on Android. Default choice I would say.

[–] flameleaf@lemmy.world 6 points 3 days ago

Thunderbird. It feels right at home paired with Firefox, and has extremely powerful message filtering built in.

Got FreshRSS running on my home server and feeding a couple of client programs. RSSGuard on my computers and Readrops on my phone. No complaints, got it doing exactly what I want it to do.

[–] osanna@lemmy.vg 1 points 3 days ago (1 children)

if you want self hosted, FreshRSS is the gold standard.

[–] llii@discuss.tchncs.de 7 points 3 days ago (1 children)

FreshRSS

It's vibe coded. :(

[–] osanna@lemmy.vg 3 points 3 days ago (2 children)

Ugh. Is there anything that’s NOT vibe coded :/

[–] boonhet@sopuli.xyz 2 points 2 days ago* (last edited 2 days ago)

Does "messages from God" count as vibe coding? If not, TempleOS is not vibe coded.

As for RSS readers, you could try QuiteRSS which hasn't had a commit in 5 years

[–] llii@discuss.tchncs.de 3 points 3 days ago

Yeah, it's a real pity. Even Dokuwiki, which was rock solid for ages, is plagued by it.

[–] Gormadt@lemmy.blahaj.zone 16 points 3 days ago (1 children)

YouTube broke my RSS feed for YouTube subscriptions by breaking how embedded videos works.

Now when I try to click on videos in my RSS feed it just gets me "Error 153" every time.

It's so frustrating!

I'm currently using Feedbro on Firefox (the add-on hasn't been updated in 2 years) but if anyone has any recommendations that don't get that error I'm all ears!

[–] ishartdoritos@lemmy.zip -3 points 3 days ago (1 children)

These days you can probably vibe-code yourself the perfect RSS extension or even standalone app.

Might give it a shot actually.

[–] JTskulk@lemmy.world 1 points 2 days ago

I've coded this and I'm a retard. Relative portion from a method:

from urllib.request import urlopen
            foundrss = False
            for line in urlopen(self.channelurl):
                for word in line.split():
                    if foundrss:
                        if not self.feedurl:
                            self.feedurl = word.split(b'"')[1].decode("utf-8")
                            if 'xml' not in self.feedurl:
                                raise Exception("'xml' not found in feedurl")
                        elif not self.channelname: # feed url is set, extract the channel name that comes soon after
                            if word.startswith(b'content='): # start collecting words
                                self.channelname = [word.split(b'"')[1].decode("utf-8")]
                                if word.count(b'"') == 2: # channel name is a single word
                                    self.channelname = self.channelname[0]
                                    return
                        else: # we have channelname started, just collect the rest of the words now
                            if b'"' in word: # get text to the left of "
                                self.channelname.append(word.split(b'"')[0].decode("utf-8"))
                                self.channelname = ' '.join(self.channelname)
                                return
                            else:
                                self.channelname.append(word.decode("utf-8"))
                    elif word == b'title="RSS"':
                        foundrss = True
[–] JuvenoiaAgent@piefed.ca 18 points 3 days ago (1 children)

I remember using XSLT to make my site's RSS look good around 20 years ago. I thought it was so cool, though XSLT was awful to write.

[–] GreenKnight23@lemmy.world 1 points 3 days ago

XSLT is a fucking curse upon all who learned it.

it deserves to be lost and forgotten.

[–] Clent@lemmy.dbzer0.com 20 points 3 days ago (1 children)

There are libraries that can polyfill this with almost zero effort. List should not effect any active site that offers rss feeds.

[–] Feyd@programming.dev 2 points 2 days ago

It's not zero effort at all. For XML(which RSS is) with xlst it is serving only 2 static files. The XML file with a reference to the xlst file, and the xlst file.

The XML can be read without transformation by tools like RSS readers, but displayed with transformation into HTML for viewing in a browser with the xlst.

You're saying it is easy to polyfill, but involving JavaScript at all completely breaks the (useful) paradigm

[–] deegeese@sopuli.xyz 12 points 3 days ago (2 children)

Who TF is still using XSLT?

Good riddance.

[–] smh@slrpnk.net 10 points 3 days ago (2 children)

We use it at my library/archive to convert EADs (XML finding aids) into something we can present to a human.

This change breaks something that's been working for us without issue for over a decade, and it's personally a PITA because I'm the only dev-adjacent person in the library and fixing this takes me away from other stuff. (I'm spread thin and we've been in a hiring freeze for 5 years. I love my coworkers but there's so much work stuff I have to deprioritoze in order to do the important stuff, it feels unfair when a big corporation decides to break something on me.)

[–] confuser@lemmy.zip 3 points 3 days ago

Dayum that's rough

[–] Lemming6969@lemmy.world 1 points 3 days ago (1 children)

You just need literally anything else other than the native browser to do it no?

[–] smh@slrpnk.net 1 points 3 days ago (1 children)

I can't guarantee an online researcher/visitor has anything other than a browser and I sure as heck don't want to walk them through installing something on whatever machine they're using. I do enough tech support as it is.

Current plan is to have the web server do it, it's just another thing on my plate that I need to figure out how to do.

[–] Giloron@programming.dev 1 points 3 days ago

XSLT can be run on the web server. The browser just receives the output HTML.

[–] wewbull@feddit.uk 5 points 3 days ago

Should never have been in the browser anyway.

[–] vortexal@sopuli.xyz 5 points 3 days ago (2 children)

I'm a little confused about this. While I've been using RSS feeds for several years, my only experience with RSS feeds is with Inoreader. Will this cause issues with the way that I've been using RSS feeds or will I be unaffected?

[–] knightly@pawb.social 7 points 3 days ago

Only if you're using the Chrome extension, maybe. This is just Google trying to kill even the memory of Google Reader by fucking with the biggest competitor to social media in Chrome.

[–] bjoern_tantau@swg-empire.de 3 points 3 days ago

You will be unaffected.

[–] brianary@lemmy.zip 0 points 3 days ago

Sites can just use CSS.