raquuk

Yes, but in this case the plaintiff is beIN SPORTS France.

Between memorable, decentralized, and secure, you can choose at most two. I am fine with not having memorable names, as long as the tooling is right. For the most part, I don't type domain names by hand. I use bookmarks, copy and paste links, navigate websites, scan QR codes, ...

There are several decentralized schemes where the identifier is cryptographically bound to a private key, none of which I can use in my browser. Since a majority of people use a handful of public DNS resolvers anyways, these resolvers could deploy split DNS for a special-use domain, let's say ".did" (short for decentralized identity), and resolve this special TLD differently. This way people do not need special software to access websites on a ".did" domain.

Maybe DNSSEC could be mandatory and your domain name is the key digest from the DS record, although this prevents key rotation while maintaining a stable domain name.

I am looking forward to finally using DNS-PERSIST-01 for validation. No more dynamic DNS updates, DNS credentials or forwarding necessary.

Using the account identifier in the record and and LE mapping the identifier to a public key internally enables key rotario without touching the record again.

The "podman generate systemd" command from the article is deprecated. The alternative are Podman Quadlets, which are similar to (docker-)compose.yaml, but defined in systemd unit files.