Well DNS does not really split this because of the way TCP-connections are defined: The are the pair of IP and Ports of both sides. So TCP-connections are always between two locations not between two identities. That's the reason why connections get lost when changing from one network to another.
Also updating DNS entries is to slow to do it whenever you walk with your smartphone from one cell/wifi to another.
You are right. I simply wanted to illustrate the idea of id/locator split. The mapping of a fixed id to a quickly changing locator is a problem of all those schemes.
Author here: the normal text is basically black on white. Do you mean the inline code parts? There contrast might be a bit to low, yes. I'm not happy in general with it's formatting and will change it in the future. (It's the default of the template I used)
Thanks for the input!
As others said, the problem appears to be with the font. A child comment of one of your sibling comments linked to a side-by-side comparison of how your site looks (left) vs. reader mode (which I forgot about when trying to read the article): https://photos.app.goo.gl/ntvIcKSDTOfdkwAi1
Sorry, the server wasn't big enough to handle everyone coming from hn. But it's working again.
BTW: The blog is also available via IPFS: /ipfs/QmdrFfK8yc6UkPK7aCcxAZzRM7K3ZP4JPfyjjbiHsHEDVH
