m0xEE @m0xee@librem.one

@hj @mangeurdenuage
Why do people still have a problem with MS? It used to be different, but nowadays in most cases you can just not use their shit — that's it, problem solved!
Unlike with Google — I don't want to deal with neither of WebPee, Brotli, QUIC, protobuf, GRPC and whatnot — yet a lot of software that seemingly has nothing to do with Google and in some cases with Web in general, attempts to shove all this down my throat 😩

@mangeurdenuage
Well, one important problem that you would certainly encounter when using BIOS to boot Windows — you won't be able to install it into a partition greater than two terabytes — because MBR partition scheme obviously doesn't support partitions spanning beyond two terabytes. I'm not sure it's a feature though.
I expect you to have this problem with grub too, but it's easily solvable with using GPT with protective MBR and a tiny /boot partition visible in MBR too.

@millihertz
Accessing memory of an object beyond its lifetime for example.
I won't generally put input sanitisation in the memory safety issues category, should I? 🤔

@Cara
Sorry, I only have one.

@hyc
Yeah, usually gcompat does the trick.
But in this case I'm not even sure — this driver thing is supposed to be rather complex with part of it in the kernel.
Worth a try I suppose, but it's strange that it wasn't even suggested in the linked thread — most probably doesn't work. On the other hand, such a configuration is rather exotic — maybe no one just invested enough time to make it work 🤷

So, Nvidia's closed-source thing simply doesn't exist for musl-based systems: https://forums.developer.nvidia.com/t/provide-driver-for-muslc-to-install-it-in-musl-distros/219586
Not unexpected, but still kinda disappointing 😩

@Pchela121 @Rezard
Там же алюминий… или нет? 🤔

@newt
You look… wrinkly!

@relentless_eduardo
Start avoiding YouTube and sending film reels of your TikToks to random people via registered airmail! Using your distant aunt's ID!
That will teach them a lesson! 🫠

@kura
@kaia

@graf @Crux_Invictus
I would be very frustrated 🤬

(My password is "password" in like 8 cases out of 10, if it's not that, there is a very high chance I'd never remember it 🤭)

@Hyolobrika
In theory you could do this with any machine, but Macs were more fun because of this speech synthesis thing you could use with just the "say" command.
Of course once this was done for the first time, people started taking counter-measures to avoid getting "pwned" so the techniques got more elaborate, such as disguising sshd as something else, which still looked like a valid process that should be there normally, or even making own tools for remote execution 😆

@Hyolobrika
Nah, it wasn't something advanced — we've had standard images for the machines used as test beds: if you messed your test machine up, you could always boot from the network and restore the image, there was a short window in the restoration process when you could log into the machine using ssh and pre-defined password, the trick was to use it to create an extra user so you could keep access to the machine and maybe run sshd on non-standard port in case the owner decides to disable it

@AngharadHafod
CC @gemlog AFAIR, you've been collecting these "mysterious" cases.

@kaia
Gojir-r-ra! 😱

@Hyolobrika
Me and colleagues used to hack into each others' Mac Minis, which everyone was using for testing, and fooling around with built-in speech synthesizer when we had the need to convey someone has to touch grass 😂