Hash tables hosted on relays with entries update signed by peers and verifiable with npubs... the improvement over dns would be an address cant be fakeble by relays.
A better censorship resistant over dns would be achieved in the same way it is achieved for digital identity in nostr: information could be self-hosted, send to various payd and free relays. If it works for other kind of notes, it will work for hash-tables-notes.
how do you allocate/issue when two people want to use the same name?
on nostr npub is the name... or if a better solution will come, it needs also to serve the basic need of having an univoque name-system-identity for all cases, not specific to enstablish https connections...
Today the way we can be sure the nostr:nprofile1qqsw4v882mfjhq9u63j08kzyhqzqxqc8tgf740p4nxnk9jdv02u37ncpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcmq0q5s we searched is the real one is verifiyng web of trust (who from our trusted follows then follows her..) so we can apply something similar in ux. The hash table entry would intend only the npub as the name.
Oddbean new post about login | logout