It seems to me like DNN has the same set of tradeoffs as noDNS, but DNN has a global state thanks to Bitcoin. Where does DNN store the IP address that a name resolves to? Does it use nostr for this? A...
Not sure why I didn't reply to this (i guess i missed it? sorry about that), but luckily rediscovered it as I was trying to find an old post, and also I guess you may have potentially gotten your answer from demo thursdays, but answering here just in case:
Regarding Zooko's Triangle, which I've re-read his old and latest version to make sure about my understanding of it and confirm the correct criterias, which is about having a string that a user can acquire where it's Secure+Decentralized+HumanMeaningful(Specifically 'Usable')
I've updated the DNN readme to include a section about Zooko's Triangle:
https://git.nostrdev.com/freakoverse/DNN/src/branch/main#zookos-triangle--dnn
Here's a screenshot in case you want to remain on nostr / not visit the link:
Regarding your other question:
local/individual meaningful names, connection/network data (IPs, etc), and other artbitrary data, for that DNN ID/TLD, are stored in nostr events, yup.
Side note / accidental benefit:
I just realized this past week that DNN's solution to Zooko's Triangle can be utilized by Bitcoin without needing to hook to and rely on a DNN nodes, inadvertantly creating a solution to Bitcoin's receive address problem, turning 'bc1qxy2kgdygjrsqtzq2n0yrf2493p83kkfjhx0wlh', for example, into:
'nabobAbove'
Regarding Zooko's Triangle, which I've re-read his old and latest version to make sure about my understanding of it and confirm the correct criterias, which is about having a string that a user can acquire where it's Secure+Decentralized+HumanMeaningful(Specifically 'Usable')
I've updated the DNN readme to include a section about Zooko's Triangle:
https://git.nostrdev.com/freakoverse/DNN/src/branch/main#zookos-triangle--dnn
Here's a screenshot in case you want to remain on nostr / not visit the link:
Regarding your other question:
local/individual meaningful names, connection/network data (IPs, etc), and other artbitrary data, for that DNN ID/TLD, are stored in nostr events, yup.
Side note / accidental benefit:
I just realized this past week that DNN's solution to Zooko's Triangle can be utilized by Bitcoin without needing to hook to and rely on a DNN nodes, inadvertantly creating a solution to Bitcoin's receive address problem, turning 'bc1qxy2kgdygjrsqtzq2n0yrf2493p83kkfjhx0wlh', for example, into:
'nabobAbove'
1❤️2
