I mean, as far as I know, DNS is decentralized. Anyone can host their own DNS server, or change which server their network/device uses. Google's is just very commonly used because 8.8.8.8 is easy to remember, but there are thousands of others run by entities big and small, and there's nothing stopping you from running your own (assuming you manage to get a hold of a static IPv4)
Nawor3565
Yes. But they get a free AC unit that could be spreading black mold spores through the air, so maybe not as good as it sounds.
And.... Now she has a $600,000 medical bill to pay off :(
I had Invisalign for 3 years, my partner had braces for 5. We both agree that the pain was far worse in the beginning when they're really wrenching your teeth into place, and then gets a lot better once they start doing the more precise movements, which take up a good chunk of the total time.
Like all medical procedures though, it can be different for everybody.
I'm a bit confused, is it supposed to say "Gmail" instead of "Google"? Gmail is their email service, but this should be comparing web search engines, no?
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.
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.
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.
If you're only going to use it from within your own LAN, then no, you don't need a static public address