5 ms·

Require the domain name to be a UUID or include the date or something else that makes it unsquattable. The domain being actually forever is far more important t

Require the domain name to be a UUID or include the date or something else that makes it unsquattable. The domain being actually forever is far more important than it being pretty. Most people will use a search engine for lookup anyway, but it's the forever domain name that is a first step in preventing links from getting broken. That said, this is not something I expect to happen in the regular Web, this seems to be a job for IPFS, blockchain or whatever. With plain HTTP, even if you have your forever domain, you'd still have the issue that the webserver it is pointing to can change, break or just disappear.

arinlen 4y ago
> Require the domain name to be a UUID or include the date or something else that makes it unsquattable. What's the benefit of a UUID over a raw IP address?
- kube-system 4y ago
  Certificates?
  - arinlen 4y ago
    > Certificates? Not a technical requirement. Subject alternative name (SAN) certificates support IP addresses.
    - tialaramex 4y ago
      More clearly, "SAN certificates" aren't a thing. Since PKIX all certificates in the Web PKI were required to have the Internet's names on them as SANs. For several years now, web browsers only look at the SANs to make decisions. The Common Name from the X.500 system is only there for humans to look at, and for legacy software which still thinks that's a good idea decades after we explained why it isn't. Ideally we'd one day get rid of it (wastes bytes on the wire), but I won't hold my breath. Unlike the Common Name, which is arbitrary human text (so e.g. " oops.example" is a valid name despite that space at the start, as are "c-programming.example\0\0\0" and "Ł0Ł.example") the SANs are defined so that it's harder to screw up and a machine can reliably just bit-for-bit compare the data. There are two main kinds: IpAddress SANs are defined for the IPv4 or IPv6 address just as bits, you can't express 200.300.400.500 as an IpAddress, whereas that's a (stupid but) valid Common Name; DnsName SANs are defined using a restricted character set and as specifically the ASCII LDH DNS hostname subset, which makes it much less tempting to try to incorrectly write a Unicode name here, what's actually required is the ASCII LDH name, ie Punycode.
- deleted 4y ago
  [deleted]
- xigoi 4y ago
  You can change the hosting for the website.
- IYasha 4y ago
  IP addressess change. In my practice not-so-small hosting provides made a few changes in last 10 years.
  - bzxcvbn 4y ago
    Do you also expect to get a forever DNS server that will host your zone without ever getting paid?
bombcar 4y ago
You’ve described an onion domain basically.

arinlen 4y ago

> Require the domain name to be a UUID or include the date or something else that makes it unsquattable. What's the benefit of a UUID over a raw IP address?

kube-system 4y ago
Certificates?
- arinlen 4y ago
  > Certificates? Not a technical requirement. Subject alternative name (SAN) certificates support IP addresses.
  - tialaramex 4y ago
    More clearly, "SAN certificates" aren't a thing. Since PKIX all certificates in the Web PKI were required to have the Internet's names on them as SANs. For several years now, web browsers only look at the SANs to make decisions. The Common Name from the X.500 system is only there for humans to look at, and for legacy software which still thinks that's a good idea decades after we explained why it isn't. Ideally we'd one day get rid of it (wastes bytes on the wire), but I won't hold my breath. Unlike the Common Name, which is arbitrary human text (so e.g. " oops.example" is a valid name despite that space at the start, as are "c-programming.example\0\0\0" and "Ł0Ł.example") the SANs are defined so that it's harder to screw up and a machine can reliably just bit-for-bit compare the data. There are two main kinds: IpAddress SANs are defined for the IPv4 or IPv6 address just as bits, you can't express 200.300.400.500 as an IpAddress, whereas that's a (stupid but) valid Common Name; DnsName SANs are defined using a restricted character set and as specifically the ASCII LDH DNS hostname subset, which makes it much less tempting to try to incorrectly write a Unicode name here, what's actually required is the ASCII LDH name, ie Punycode.
deleted 4y ago
[deleted]
xigoi 4y ago
You can change the hosting for the website.
IYasha 4y ago
IP addressess change. In my practice not-so-small hosting provides made a few changes in last 10 years.
- bzxcvbn 4y ago
  Do you also expect to get a forever DNS server that will host your zone without ever getting paid?

bombcar 4y ago

You’ve described an onion domain basically.