Oh, true, I have that! Will try, thanks!

Though, in the end, using an NVMe USB enclosure is never good in an way

Same thing, but with an external NVMe enclosure and it crashing the whole USB Bus of my MB it was plugged into until poweroff and poweron (not reboot!), meaning my peripherals disconnected too. Basically fixed by moving it to the front USB-Ports, now it crashes much rarer (previously a minute of playing MC with the profile residing on the NVMe would crash it, but not hours of RDR2 or similar. Very weird. Not it does after a few hours of MC), and can reliably be recovered by replugging.

Still looking forward to a new PC with more that one NVMe-PCIe Slot though.

Basically, yes. There are many ways. But:

An anti-xray plugin is nowadays as common for servers as lithium or essentials. It either removes all important blocks from view, inserts fake blocks (eg. ores) or just makes everything appear as only stone. The middle option can even serve as evidence of a player using xray. For preventing ESP, you can do effectively the same but with players: Hide them and their particles until they’re in view, and randomize their sounds’ position, so that a client mod does not provide any more advantage than having decent headphones.

Server-side culling essentially.

Minecraft is actually a good example.

Server owners pay very little to nothing for anticheat, and cheaters have dozens of extremely elaborate clients to choose from, all interfacing with the very open and moddable game. And still, servers that do give a fuck have basically zero rage cheating. ESP? Sure, but that can be solved as well. But beyond that, everything can and is detected. And that in a game as sandboxy and freedomy as MC. It was designed to have a lot of slack in movement and actions, yet ACs are extremely good.

Easy:

1. Swap MB
2. reinstall Bootloader
3. You’re done

Bonus for switching devices:

1. Liveboot on receiving device, do nc -lp 42069 > /dev/sda (or whatever disk you want)
2. Liveboot on original device, do dd if=/dev/sda | nc <Receiving IP> 42069
3. Reinstall bootloader, maybe change fstab

Problems I had:

• Had to uninstall old drivers (eg. Nvidia)
• Had to redo systemd-creds, as the receiving server had no TPM

Even Email can be down for two days or so without major consequences, and I could pull that up from backups on a spare server in another location within an hour max.

I’m also localhost:8080’ing now

My primary scare is wg being another potential single point of software failure, preventing remote access

Fuck me, I sometimes just do a find / -name “*.pacnew” and diff manually

$()

Backticks are pretty old syntax.

Ah, and not being able to play the game I bought for 40 fucking dollars is of course fine then.

Proton, nice return policies, the best launcher, disclosure of BS like ML, other launchers, kernel level anticheat. Just a few.

Relative to his wealth? No. Relative to others? A lot.

I hate misused taxes.

Gabe at least gives us 95% greatness back (5% being gambling)

Valve promises greatness, but fucking DELIVERS

The solution to all of your problems:

echo ‘echo UwU senpai’ >> ~/.profile

Misunderstood instructions, have a tailplug in me now UwU

Not necessarily. Maybe they reboot directly into their code, flashed on their MB?

Though, the central reason for everything should be the most important part: capitalism.

Then stop spamming. I can just as well tape your eyes open, write that shit on your contact lenses and tell you to just look somewhere else.

Generally: Disks with Luks have to be opened first before being able to be mounted. After opening, a virtual blockdev is created, with the UUID you put into fstab. As the Luks disk is not unlocked at boot, the virtual blockdev doesn’t exist yet, so systemd hangs for 3 mins or so trying to find/wait for it to mount it

Usually, it should continue to boot after timeout. If it does not, you need a USB Stick with Linux, boot that, mount the root partition and edit the fstab