One more idea… If you’re willing to temporarily add the Debian testing “deb-src” repository to your sources.list, which should be slightly safer, then there’s a chance that this might work: https://wiki.debian.org/SimpleBackportCreation

Seems not completely crazy, unless MX has its own way to do that.

Yeah, I see that MX test is not based on current debian testing (trixie) but also bookworm. So I guess you’ll not find the package in MX repos until it makes it into AHS. Apparently there’s a PPA that some people use, that might work.

Ok, it didn’t seem clear if you were on Debian 12 or MX. I’m not sure what the relationship between them is, but mesa 25 seems to be in trixie only since 13 march.

Maybe you could use that package from debian testing on the MX version of testing if you wanted to live dangerously.

At this point in the debian release cycle your easiest course of action would probably be to switch over to debian testing. It’s quite easy to do if you’re in debian 12 and wanting newer packages is a legit reason to do it. It should be getting reasonably close to being stable by now I would guess.

You’ll need a newer kernel than is currently in debian stable as well, but that is actually quite easy to build and install. Building mesa I don’t know about, but it will have many more dependencies and could be a lot of work.

Oh yes I did fail to include a full catalogue of all the base instincts it obviously appeals to — but it’s as if people are eating a giant pile of shit for breakfast, and you’re helpfully explaining that well, we all need to eat.

oh I would quit X, but I’d miss [ politicians / my friends / the latest gossip / the hottest memes / Stephen King ]

It might’ve seemed to make sense in 2016 but that bullshit doesn’t fly any more. It no longer takes any imagination or courage to see it for what it is. There are no more excuses.

I used to think that the worries about social media algorithms exerting some kind of profound mind control on the users were overstated, but holy fuck, what kind of perverted sci-fi brainwashing power does twitter have that people are still using it even in the year 2025?

It’s not as if humans slavishly obeying the algorithms was a much better situation than robots doing it. They’ve just sped up the process and it can only hasten the demise of the new technofeudalist content mills.

I think you’ll find most phones come with a web browser. But I can confirm that I do use Vim to edit the list.

Apache and nginx are two of the better-known grocery list servers. Just put a text file in /var/www/html.

Good luck GNOME users! If Xfce ever added a donation button I would not be donating again.

Oh yeah, I remember debian’s Firefox used to be called something else for trademark reasons some years ago. I wonder how much linux market share firefox lost as a result. Not sure what changed, I guess in that case Mozilla must’ve come to their senses. I was mostly an ubuntu user in those days.

… lwn has the story: https://lwn.net/Articles/676799/

Telemetry can be turned off without modifying the code. I don’t know about the legality of it, maybe in the case of Firefox the other things they do are also at most build options rather than code changes. But generally distros are allowed to make changes to the packages they distribute, that is how free software works.

I wonder if mine would’ve been counted there. Even before I switched to Librewolf, Debian disables most of the telemetry.

That would depend on the parameters of “possible” but it has no bearing on the topic at hand. It seems likely that you ask due to mistaking the idea of not requiring everything to be periodically re-signed by Mozilla in order to keep running for the unrelated idea of not checking the signature at all.

P.S. Okay that may be slightly wrong but I mean it’s not as if two-years-old keys are automatically compromised just because they’re that old. If there’s reason to believe they’re at risk, let them be revoked for cause.

There are many slightly different options I suppose, but personally I’d start with the simple and obvious approach suggested by the principle of least surprise: Check the expiry date on the extension signing cert only when an extension is installed. On subsequent startups, attempt to check for revocations.

Software should not self-destruct if it can’t reach the mothership.

Signing certs should be expected to expire. Already-installed browser extensions signed by them should not, when the user doesn’t want them to.

Doing it the right way would prevent, for one thing, any possible repeat of the problem they had a couple years ago when they simply forgot to renew the cert and one day everyone’s browsers unexpectedly stopped working with no way to fix them short of making a new build. The debate was had then, you can go back and read what was said. A thorough review was promised. Presumably Mozilla came came to the wrong conclusion and decided it would be best not to publicise it much.

They’ve removed the ability to do it through the normal settings menu a few years ago, so you’d have to type about:config in the Firefox url bar and do it there. You’ll get a warning about how dangerous it is, and then you can type the names of preferences you want to change and double-click on them when they appear to turn those ones on or off. Turning off EME can be safely done without any side effects, but it’s not recommended to change anything else in there unless you know what it does.

It would mean you can’t watch e.g. Netflix and some TV station websites won’t be able to play video — although I’ve found that on others, the TV programs play just fine but the ads don’t work.

Have they fixed the problem properly yet, or is there a future expiration date coming for the new version as well?

Librewolf and the “EME-free” builds of Firefox are the two I know of. You can also set media.eme.enabled and browser.eme.ui.enabled to false in any Firefox-based browser.