Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Add DNS DEP #25
My only blocking request is for a privacy/security section. This section should lay out assumptions and a trust model (who is trusted? what information is considered public or private?), and address the privacy difference between approaches (or this could be expanded on in the Alternatives).
As comments (but not blocking things that need to be addressed): i'm sad that there are basically only large hyper-centralized DNS-over-HTTP providers today (google and cloudflare).
A little concerned about semantic confusion to users between addressing-by-name and addressing-by-key/hash: the names are more usable, but have different security/robustness properties and it's confusing to have to explain the difference (hashes are already confusing). From a robustness/archival/scholarly/fixing-the-broken-web perspective, it's also really nice to use opaque strong links (aka, hashes) instead of DNS names that change hands, become un-registered, and suffer "content drift".
My preference would be to encourage folks to use hash-style links and address the confusion challenge head-on.
(This isn't a new thing with this proposal, just commenting my feels on using names in general. I think the human-naming challenge should be kept modular; aka Dat should not try to solve this in a Dat-specific way, the dweb community/ecosystem should try to solve this in a general way that will help all projects).