The url that ends with it and io are still registered by icann right? Even if you paid for them with sats for opsec reasons. So without icann giving you permission to use the url you couldnt have done this? Or am i mistaken.
Nostr prompted me to redesign my entire online presence:
- Personal website: Built using nostr:npub1pr4du5xl28dy5sh4msz9uddnwxgzupkk4qzjzklv84edc6ruevzqlxmkzp, it aggregates long-form articles published with nostr:npub1w0rthyjyp2f5gful0gm2500pwyxfrx93a85289xdz0sd6hyef33sh2cu4x, and it uses a custom domain courtesy of nostr:npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxy.
- Contact page: While still hosted on Github, it now embeds a contact form created with nostr:npub1qu7dsd44275lms4x9snnwvnnmgx926nsppmr7lcw9dlj36n4fltqgs7p98, an amazing Nostr-based form builder service
- X/Twitter, Facebbok, and LinkedIn: I've pinned posts announcing Nostr as my new home. This is also my advice to you: don't delete your existing social media accounts, keep them active to direct your audience to Nostr.
Discussion
You are perfectly right.
Actually, things are even worse: all .io domains may soon disappear for geopolitical reasons.
Once, I hoped Namecoin/Bitcoin could give us a permissionless DNS, but it did not happen. Could Nostr be a new tool for that goal?
I wrote more here:
nostr:note12vy6ll7vg5vjepf5s3gyn7wajlwgg34efddlf2zcddr9r76h5caszg3frz
I have this on the back-burner as a way to avoid a centralized resolver: https://github.com/pubkeychain/pkc-protocol But most people don’t seem concerned with this so there is no urgency yet and hence no implementation or even real interest.