Them being subject to the pretty draconian laws of Germany is a minus for most people if they had no other reason to have to follow those laws (such as not being in Germany).
Somebody that is based in Germany (which is what GP was recommending .de for) is usually subject to German law, due to... being in Germany.
And conversely, when not based in Germany, you'd need a proxy Administrative Contact anyway. (Registrars can probably provide that for you, but it seems like asking for trouble.)
If it's not strictly non-commercial then you have to publish your fill name and home address prominently on it. You can't say anything insulting about anyone, even if true. And you can't criticize what Israel did because it's considered antisemitism.
> If it's not strictly non-commercial then you have to publish your fill name and home address prominently on it.
Under German law, as far as I understand this is true for publications "addressed to a German audience" regardless of your domain's TLD, your server location etc.
Public means the government. So that means it's harder, not impossible. That's good news because it means the situation isn't totally fucked, and it's probably legal to compete with the incumbents, and even have the unofficial blessing of the city (they like what you are doing so they grant all your digging permits).
By the equally lazy and possibly bullshit method of "ask ChatGPT a follow-up question in your conversation" I learned that these laws are only about municipalities - private businesses are not restricted this way from deploying networks, even within a municipal region.
Every time someone complains about their ISP I encourage them to think about starting their own. If you're a nerd it doesn't seem impossible at all - in fact it's happened many many times before. Obviously, a lot of people need stable jobs and the like, but if even a small percentage of people end up taking some steps, that's great.
It is, but since we rely on DNS anyway, no matter what, and your DNS provider can get a certificate from Let's Encrypt for your site, without asking you, there's merit to combining them. It doesn't add any security to have PKI separate from DNS.
However, we could use some form of Certificate Transparency that would somehow work with DANE.
Also it still protects you from everyone who isn't your DNS provider, so it's valuable if you only need a medium level of security.
There is no need for a certificate from let’s encrypt. DANE lets you put your own self signed certificate into DNS and it should be trusted because DNS is authoritative, although DNSSEC should be required to make it secure.
And yet no browser trusts it, and a single-digit percentage of popular zones (from the Tranco list) have signatures; this despite decades of deployment effort. Meanwhile, over 60% of all sites on the Internet have ISRG certificates.
reply