functional parts not being copyrightable means that you can't claim a program is a copyright violation based on the fact it does the exact same thing based on compatibility reasons (you can copy what the program does). E.g. git stores refs in .git/refs, so does grit, that's not a violation. You still can't copy the program.
Asking an LLM "here's a thing, rewrite it in Rust" is pretty clearly creating either a derivative work or a different form of the same work, just like asking a transpiler would.
Especially since sanctions are transitive. Mozilla and Google, being US companies, are actually not allowed to trust any entity whose purpose is to work around sanctions. Their members could go to jail for that.
It works like this. The US gov sends LE a nastygram saying they must terminate service to sanctioned entities. LE either does that or several people go to jail. The USgov doesn't care how it happens, as long as they can't find any evidence that any sanctioned entities are LE customers.
In the EU there is the threat of jail time if a user of your service does something bad and you haven't completed the necessary bureaucracy to be immune to it. This is the opposite of the US. See for example pissmail.
Before this, they were all unencrypted and you had to pay to get a cert. I guess we could go back to that - now knowing that every unencrypted connection is being MITMed (the world is so much more hostile now)...
Yes actually you still could've. But it would require a pass through the IETF to stabdaddize a DNS record type, and that would delay Netscape's release.
If each country could only sign its own domains it would make sense. If the US could only tamper with .us domains the system could be trusted in general. After all, that's no worse than what they already do by coming to your house and putting a gun to your head.
Domain registries can already get a certificate for your domain by changing the address to their own server temporarily and then doing ACME with LE. So no new vector is introduced by directly putting the cert in DNS.
CT seems useless for DANE because the cert is self signed, so anyone can just flood the CT with self signed certs for your website. It's useful with WebPKI because only certs signed by a CA go in CT and it's a big deal if one is mis-issued. Anyone can mis-issue a self-signed cert at home for fun.
We all knew something like this was coming when we decided to centralise the web around Let's Encrypt.
In reality of course you can probably just ignore this as long as you request the certificate from a proxy in a nonsanctioned country and you don't stick out to the government.
I think the only way to deal with that right now is to hire a company whose job is to deal with it. They'll random-check your outgoing emails are indeed what you say they are, and they maintain a reputation with the big providers for checking it properly.
What pre-validation could you do that would possibly be useful?
If you try to create a Discord account with Firefox Klar as your default browser, on Android, immediately upon signing up you'll be banned. I have to assume this is because it clears cookies and thinks you're a bot farm.
You know what does this better than a humanoid robot? A toilet with a built-in dispenser for mild chemicals! It could do it periodically, or with every flush so that the mild cleaning chemicals are always sitting there. An unsophisticated one made of cheap plastic could be bought for $5 a the grocery store and clip onto the side.
Indeed. It says they rely on two different substances which normally don't mix (nitrates and sulfites), presumably because if they were both present at the same time they'd react with each other directly without the bacterium extracting any energy from that. So they live in places that sometimes have one and sometimes the other, and have to store one of them until the other comes along, which can be years. Or that's how I read it.