So yeah, you can sue for anything. But even if you know you’d never win the lawsuit, you can tie the other person up in court and waste their time and money.

No. They’re literally a meme for how bad they are on tech content: https://knowyourmeme.com/memes/events/the-verges-gaming-pc-build-video

Yes, and that’s a good thing if you don’t want it to start killing processes. You have that extra time/space to deal with the out-of-memory condition yourself.

Or you can ignore that condition and continue using the system in a degraded state, with swap as “disk RAM”.

No, but Windows is so entrenched that they don’t need to actually be competitive in order to keep making profit. Instead, the Windows team has to invent things nobody ever wanted or needed that they can advertise to make it look like they’re still useful. Software UX polish-passes don’t make good marketing. You can’t seriously put “you know that one weird thing that only happened to a fraction of users sporadically? we fixed it” on a marketing campaign.

Nobody. And it’s not like Red Hat runs the X.Org Foundation, either, at most they have one seat on the board. Development will continue.

it’d be real cool if the mods of the biggest community on lemmy.world would actually do some moderating

ISP shittiness aside, ISPs do actually pay for Internet backbone access by the byte. Usually there are peering agreements saying “you take 1tb of traffic from us, and we’ll take 1tb of traffic from you”, whether that traffic is destined for one of their customers (someone on Comcast scrolling Instagram), or they’re just providing the link to the next major node (Comcast being the link between AT&T’s segment of the US backbone and Big Mike’s Internet out in podunk Nebraska).

And normally that works pretty well, until power users start moving huge amounts of data and unbalancing the traffic.

I’m not sure what that post is meant to show, if swap isn’t “disk RAM”. That post even concludes:

Swap […] provides another, slower source of memory […]

PSoD is already used by VMware ESXi. And Windows Insider builds, I think.

Maybe green?

If it’s only on the ESP, it won’t persist across reinstalls, and definitely not drive swaps.

But I do see mentions of attacking via firmware capsule. If that works, then yes, that will persist.

How? You could certainly temporarily break the boot process, but I can’t see how you’d completely brick it.

My favorite is when the sssd package maintainers don’t properly update their dependencies, so when some of the packages get updated, they don’t pull in others, and then I’m not able to log in with my external account.

It depends. I’ve used a chargeback where I sent a product back for a warranty repair, and the seller stopped responding. The bank just wanted documentation, and they put it through. I imagine you could argue for a chargeback in this case, if you used a credit card.

Also tell the person administering it to do it slowly. In my experience, most of the pain was from them doing it too fast. Something about the fluid stretching the muscle in painful ways before it can spread out, or something.

If electric bikes were the only thing allowed on back roads, you’d never be able to make enough grocery/dump/Tractor Supply runs to have time for anything else in your life.

The monitor seems to be recommending you use mode 1280x1024. Have you tried that?

Either self-encrypting drives (if you trust the OEM encryption) or auto-unlock with keys in the TPM: https://wiki.archlinux.org/title/Trusted_Platform_Module#Data-at-rest_encryption_with_LUKS

Same. Well, not forced, but using Linux would just make everything more difficult. I like being able to drop to a shell and use a Linux environment with its useful utilities to manipulate stuff on my Windows PC.

Yeah, I could use mingw, but that is a pain, and I can’t just apt install stuff.

I can’t just run an extention cord out an open window.

This is exactly what my neighbor does in his apartment.

But he has a driveway, so it’s not like he’s running it over the sidewalk or anything.

I can’t count the number of times I had to do that under ESXi, or do manual vSAN recoveries, so I found myself quite comfortable doing that in proxmox too (especially since proxmox is regular debian).