Not sure where you're located, but at least in the USA it's definitely illegal for an employer to discriminate against a medical diagnosis like that. They aren't even allowed to ask you private medical questions during the hiring process.
Nawor3565
Funny enough, Usenet is still around too, it's used as an alternative to BitTorrent for sharing pirated stuff.
The problem is that brute-forcing passwords hasn't been a thing for ages. It's all about phishing and social engineering now, something passwords can't protect against. It doesn't seem like they're pushing for pins as much as passkeys, which I much prefer using over other bandaid fixes like SMS 2FA (well, now that Firefox for Android properly supports using passkeys from Bitwarden. Before they fixed that, they were really obnoxious to use).
If he wanted to give it to the public domain, you don't need creative commons. CC0 is public domain, but you don't need to use it, the copyright holder just needs to state "I dedicate this media to the public domain" and bam.
And any copyright they still have over their media isn't "forever", it will expire eventually. In the meantime, yes their estate likely has the rights, whoever that may be.
Do you have a static IP address? CG-NAT has done a really great job of hindering torrents, since my understanding is that at least one side of the connection needs to have an open port. So, if you don't, then only the few people who do are able to download from you, which can make it seem like no one wants your stuff.
Tails is a bit overkill, even for this. It's not just privacy focused, it's for the same people who need to use TOR (Tails even routes all traffic through TOR by default IIRC, no?), i.e. those who are sharing classified government intel or running large darknet drug markets. Unless OP is that paranoid, they can probably start off with a basic Debian or something, which is already leagues ahead of Windows in terms of privacy.
I would not bother archiving the mainstream releases that can already be found on many torrent sites (like, you don't need to archive Star Wars or Lord of the Rings) and focus on the bootleg disks first. You just need any standard DVD drive, then use Handbreak to rip the disks to a video file. For official releases, many of them have forms of copy protection, but 15 minutes on Google should tell you how to get around any you come across.
Also, for reference, "burning" a DVD is writing data to a disk, so the opposite of what you're trying to do.
If you tried to get your newborn daughter a labiaplasty so that she would be "more appealing to boys once she's old enough", you would rightfully be scolded and kicked out of every respectable medical practice you asked at. It's fucking gross to be sexualizing a literal newborn like that, and yet I used to regularly see people on Reddit use that as a good reason to circumcise your son.
And any "hygiene" justification is just grasping at straws. Do we cut off people's ears so they don't have to spend 30 seconds cleaning them every day? No. Just teach your kids how to clean themselves and it's a non-issue.
Divide the RGB values by 255? That will give you a number between 0 and 1, so just multiply that by 100 to get the percentage. Unless I'm misunderstanding what exactly you need to input into Photoshop.
Sorry, Microsoft might make crappy software, but they aren't actively trying to invalidate my existence as a person. Absolutely not comparable.
Why would you need to block apps installing from non-Play Store sources? You shouldn't be plugging your phone into mysterious USB ports, and the OS should always prompt you before installing a local .apk file. If you're savvy enough to use F-Droid, you're savvy enough to not need that hand-holding "safety" feature.
Here's the thing: you don't necessarily need to use biometric data to store a passkey. That's how the vast majority of current implementations do it, but it's not required by the spec. Personally I store all my passkeys in Bitwarden, meaning I can lock them behind my master password with no bio data involved. It also means that my passkeys are platform non-specific and are stored on my own self-hosted Bitwarden instance instead of in some mega-corp's cloud.
As for SSH vs passkeys, AFAIK they're both based on the same encryption but SSH keys are just super low level (the raw key in what's essentially a text file) vs. the more abstracted passkey system that, in theory, is more user-friendly.