It’s the deficient market hypothesis in action: If someone has money, he must be right. Therefore, give him more money.

It’s “social media platforms such as X or Facebook” that are driving people of all ages “to the right.” By now you’d think word might’ve spread further that there’s more to the Internet than that kind of disreputable backwater.

Elon cares deeply about the truth and seems as if he has boundless energy to devote to suppressing it.

Yeah by “do whatever you like” I mean install MO2, edit the registry, run dyndolod, mess around with system dlls, whatever. One thing I’ve just learned about that might be useful: https://github.com/SulfurNitride/NaK

The “immutable” thing shouldn’t be a problem I’d think. Games installed through e.g. steam aren’t affected by that — it just does its own thing creating a wine prefix for the game somewhere in your home directory. You should be free to do whatever you like in there.

Thank Goodness You’re Here was good for a few laughs.

You can adjust the dpi setting in winecfg to fix the font size, but in recent beta versions of proton I find it necessary to set it back to the default (and restart wine) to actually play the game.

There was one fairly popular fo4 mod that didn’t work for me, but the only skyrim one I found that seemed to have a problem with linux was nemesis, and that has now been replaced with pandora. All the other thousand or so mods I tried (currently using 600 or so) seem to work about as well as they do for anyone else.

MO2 runs just fine for me. I don’t actually use it for Skyrim — I do that all manually — but it worked for e.g. Fallout 4 without me doing anything special. I just ran its installer the same way I’d run skse64_loader.exe using the same prefix as the game.

https://theanarchistlibrary.org/search?query=copyright

Meanwhile, my totally legit probably-not-a-front-for-Chinese-spies current VPN is now blocked by citizenlab.ca. Had to use tor to get there.

Yep. It sends me to fsf.org. If the link goes here or anywhere else and such things bother you, fix your “referer” settings.

They’ve been warning us about the dangers of a Cyber Pearl Harbor since 1991 but I’m not too worried: Computer systems have become much more flaky and unreliable than they were then, so we’re much better prepared for none of them working.

I was a user for a while. Never did figure out if they were just a small team of well-meaning people who didn’t know how to run a business properly, or a front for something. Good prices though, and reliable service for the time I was there. Their web page seems to indicate they got acquired by Malwarebytes, I’m not sure if that makes them less trustworthy, or more.

Taler does use crypto, aka cryptography, to make sending payments securely anonymous. That is the main point of it.

Target audience: People who want to pay for stuff anonymously through the Internet. It’s a large and underserved market.

It’s a big part of why people got so excited about bitcoin, and why it was so disappointing when it spectacularly failed to be any good at that application.

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.

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.

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