If you are willing to implement Mainline DHT from scratch, go for it. But if you are OK with using an off the shelf implementation here is how to implement Pubky from scratch:
1. Encode a DNS reply packet containing the endpoints you want, for example www. A 3600 IN vitorpamplona. com
2. publish that packet using Mainline PUT mutable rpc method using an ed25519 keypair.
3.on a different machine, make a GET query with Mainline for the Public key from step 2
4. once you resolve the encoded packet parse it and find www.
congratulations, now you made https://www.
there is of course more to it like work on a home server that stores your data for you and republishs your packets on Mainline periodically and offer a simple but open api, etc.
but the main thing here is what I described above, if you don't think that is valuable, then that is fair.
If you don't want to start from scratch, then you can do what I just described using this GUI https://app.pkarr.org , or if you can tolerate rust, you can go to https://pkarr.org where you can read more about the system, but also use the examples in the pkarr directory to publish and resolve packets and get a feeling for the speed and reliability.
so, does a censorship resistant DNS that can fade in the background and be taken for granted by web developers and make all the rest of web technologies usable in a more sovereign way and offer a credible exit from cloud hosts, does any of that sound interesting?
happy to answer more questions.
