AnyOldName3

Of course not, but it's an unrelated not fine to whether or not someone's a tankie.

That's not relevant to being a tankie as the US, Israel, and other states backing Israel, aren't claiming they're building communism or are the successor state to another which claimed to be building communism. It's the part where communism is an excuse that means the bad things didn't really happen and would be fine even if they did that makes tankie-ism its own distinct thing.

Upstream Firefox doesn't comply with FDroid's rules (thanks to the 'proprietary bits and telemetry' Handles mentioned), so is only available from the Play Store or as a loose APK that won't auto-update.

It's not realistic to demand to own games in the same way as a spoon any time soon. It is, however, pretty reasonable to demand you own games like you'd own a book. You can chop up a book and use it to make a paper maché dog, but you can't chop up the words within to make a new derivative book (or just copy them as its to get another copy of the same book except for a single backup that you're not allowed to transfer to someone else unless you also give them the original). The important things you can do with a book but not a game under the current system, even with Gog, are things like selling it on or giving it away when you're done with it and lending it out like a library.

About a hundred years ago, book publishers tried using licence agreements in books to restrict them in similar ways to how games and other software are restricted today, but courts decided that was completely unreasonable, and put a stop to it. In the US, that's called the First Sale Doctrine, but it has other names elsewhere or didn't even need naming. All the arguments that applied to books apply equally well to software, so consumers should demand the same rights.

As a counterpoint, I've had Ubuntu's installer and grub's updater overwrite and break Windows' boot files several times, but never had the opposite happen (I've had both destroy themselves, though). Thankfully, I know how to rebuild the necessary parts of a Windows install, so it's never been a catastrophe, but it's irritating to see what's always been the source of the problems I've had be held up as infallible. Possibly this is a problem unique to Ubuntu - I'm happy to blame Canonical - so maybe it could be entirely sidestepped with other distros.

I'm not arguing for anything in the post above, just pointing out that a broken (or badly repaired) insulin pump is genuinely more dangerous than having no insulin pump. That doesn't have to count against the right to repair one, as if you've got the right to repair an insulin pump, and do so badly, it doesn't mean you're legally forced to use it afterwards, just like I've got the right to inject all the insulin in my fridge with an insulin pen back to back, but I'm not legally forced to do so.

I do think the right to repair should be universal, but as I think that medical stuff should be paid for by the state, NHS-style, that would end up meaning that the NHS could repair medical devices themselves if they deemed it more economical to do so and recertify things as safe than to get the manufacturer to repair or replace them. The NHS is buying the devices, and gets the right to repair them, and that saves the taxpayer money, as even if they don't actually end up repairing anything, it stops manufacturers price gouging for repairs and replacements, and if the manufacturer goes bust or refuses to repair something, there're still ways to keep things working. It doesn't mean unqualified end users can't use their new right to repair their medical devices and risk getting it wrong, but if you've got an option of a free repair/replacement, most people would choose the safe and certified repair over their own bodge.

If you've got a broken insulin pump, assuming you're in a country with a functioning healthcare system, you should have been given a spare pump with the original, and probably some insulin pens, so when one breaks, you fall back to the spare, and get given a new one to be the new spare (or could get the broken one repaired). Using the spare is completely safe.

If you don't have a spare, your sugars would go up over several hours, but you'd have a day or two to get to a hospital and potentially several days after that for someone to find you and get you to a hospital, so it's not safe, but also not something you'd die from if you had any awareness that there was a problem.

If you've got an incorrectly-repaired pump, you could have it fail to give you enough insulin, and end up with higher sugars, notice the higher sugars, and then switch to the spare. That'd be inconvenient, but not a big deal. However, you could also have it dump its entire cartridge into you at once, and have your sugars plummet faster than you can eat. If you don't have someone nearby, you could be dead in a couple of hours, or much less if you were, for example, driving. That's much more dangerous than having no insulin at all.

Prosthetic legs don't have a failure mode that kills you, so a bad repair can't make them worse than not having them at all, but insulin pumps do, so a bad repair could.

Nuclear is even less killy than hydroelectric (dams sometimes burst and drown a bunch of people downriver) and wind (sometimes technicians fall off when fixing a turbine) per kilowatt hour, despite the potential for really scary failures, largely because it generates so much power when it's working.

It's easy to get pressured into thinking it's your responsibility. There's also the risk that an unhappy company will make a non-copyleft clone of your project, pump resources into it until it's what everyone uses by default, and then add proprietary extensions so no one uses the open-source version anymore, which, if you believe in the ideals of Free Software, is a bad thing.

There was an EU-wide one that gota lot of its funding redirected to AI stuff recently that you might be thinking of.

No, that is an entirely unrelated bad decision. It being okay to not have a popup to opt out of secure boot when it does its one job and notices you're about to run insecure code in kernel mode doesn't make every other user-hostile thing Microsoft ever does magically okay.

It's upstream GRUB that's decided the older GRUB versions are insecure and not to be trusted. Microsoft just propagated that to machines running distros that weren't shipping patched GRUB builds yet. Up-to-date Debian wouldn't be affected provided that they downstreamed fixes quickly.

https://fedia.io/m/linux@lemmy.ml/t/1111595/-/comment/6916699 says that Debian's GRUB wasn't affected, but another part of the boot sequence was.