Jesus, if you're still using a browser that like 10 major versions old, you've got bigger problems than worrying about a privacy plugin no longer being supported!
this post was submitted on 12 Mar 2025
22 points (100.0% liked)
privacy
3493 readers
3 users here now
Big tech and governments are monitoring and recording your eating activities. c/Privacy provides tips and tricks to protect your privacy against global surveillance.
Partners:
- community.nicfab.it/c/privacy
founded 2 years ago
MODERATORS
It's all add-ons, not just Privacy Badger.
Ah, I thought it was add-ons by that developer.
But still, nobody should be on such an old build of any browser - for security and privacy sake.
I wonder how this will effect Pale Moon.
Their changelogs seem to be pretty up-to-date, so I would assume they are on the latest FF codebase, no?
It's long been departed from the Firefox codebase.
My ponderings did end up being pointless, though: it turns out they never even supported MV2 Firefox extensions.
Or you have an extended OS support contract. And that's something even small biz uses. Er, so I've heard.
But carry on. Stale stuff is bad stuff, apparently, but I can see 7 rail lines from my window.
Extended OS support has little to do with using outdated browsers. Firefox 115.13 should run on any OS that can run 115.12 and it doesn't have this problem. Versions older than 115.21 have critical security vulnerabilities and should not be used in an environment where they could load untrusted content from the internet.
Jesus, if you’re still using a browser that like 10 major versions old, you’ve got bigger problems than worrying about a privacy plugin no longer being supported!
Versions are meaningless. It's just numbering.
128 came out in July of last year, which means that Firefox will deliberately block use of products after eight months.
That's fucking garbage. Software development and release lifecycles have turned into a "release-ignore-discontinue" cycle of barely long enough for consumers to constantly upgrade to.
128 came out in July of last year, which means that Firefox will deliberately block use of products after eight months.
Is there a way to find out how many security specific fixes were introduced in those 8 months?
I would agree with you only if the version updates were purely cosmetic, but I tend to see security patches with nearly every release. And 8 months sounds like an eternity to not be patched up.
They aren't deliberately blocking anything, but rather certificates are expiring.