r00ty

Linux secure boot was a little weird last I checked. The kernel and modules don’t need to be secure boot signed. Most distros can use shim to pass secure boot and then take over the secure boot process.

There are dkms kernel modules that are user compiled. These are signed using a machine owner key. So the machine owner could for sure compile their own malicious version and still be in a secure boot context.

They’re deporting themselves now too? That’s efficient.

They send fake (non-existing) actor ids for votes to obfuscate the identity of the real user. It is “compliant”, but completely against the spirit of a public social network.

There have been discussions about how to implement this before. But it has to be done in a way that is agreed by other threadiverse software. Unless they actually provide profiles for these fake actors there will be problems since some software will look up the profile info to cache it, even for likes…

Personally I’m of the opinion of a standard header to mark a favourite message as a private one and use a random ID that the originating instance can use to validate the message as genuine. But, this needs to be adopted properly by all.

I bought my first HDD second hand. It was advertised as 40MB. But it was 120MB. How happy was young me?

And just to show I’m serious, you have zero seconds to comply.

This seems quite similar to what we call I’m the UK inverse snobbery. It was quite a big thing (apparently) during ww2.