One of the disadvantages of the "public" DNS system, is there are companies[2] and governments[3] (sometimes having a history of oppression[4]) that can interfere with it. GNUnet on the other hand, is actually public.
[1]: https://www.gnunet.org/fs-urisyntax
[2]: http://arstechnica.com/security/2014/06/millions-of-dymanic-...
[3]: https://www.wired.com/2012/03/feds-seize-foreign-sites/
[4]: http://www.sfgate.com/news/article/Black-Friday-birth-of-U-S...
The thing I don't like about it is the distributed hash table aspect, making it a "publish by default" system (with some obfuscation, but still). All that is really needed is a way to communicate your petnames with people you want to have access to them. I'd rather that be done more privately. Besides that, I think the system is a great way to do distributed names to values (send keys with names is much better than PKI).
URIs are incredibly important and deserve a more solid foundation to build upon. To make them truly unique, we should use some form of GUIDs. Pet names are a usability layer on top of GUIDs for us humans , but we should communicate the GUID instead of or alongside the pet name.
It's why relative names and forkable registry is a good solution.
But in some cultural context where a registry is mainstream, names are almost unique.
Here are some explanations :
- http://seenthis.net/messages/358071
- https://gnunet.org/sites/default/files/paper_cans2014_camera...
> 3.3 Relative Names for Transitivity of Delegations
> Users can delegate control over a subdomain to another user’s zone by indicating this in a new record
They're not a good idea when they are user-friendly, because of domain squatting.
But `ebbfed3a54f82da274b51df5c5f1fcd8644edc0b5beb86643a0e177f1cb4ad60` is a perfectly good universal, unique, canonical name, and `(ebbfed3a54f82da274b51df5c5f1fcd8644edc0b5beb86643a0e177f1cb4ad60 foo)` is a good relative name, rooted in a universally-unique name.
ipfs is awesome, but I want to first be able to mount it as the file system :-)
I have zero knowledge of Go, so not even sure how to start troubleshooting.
Even IP addresses aren't strictly "unique". Very recently HN users were complaining about the same Sci-hub donation page showing different Bitcoin addresses in different regions: https://news.ycombinator.com/item?id=11636331
If everything goes right in DNS, you and I can both type "https://news.ycombinator.com/" into our browsers and end up reading Hacker News.
The workflow to get to the same end result (viewing HN) doesn't seem immediately clear to me with GNS/GNUnet. I'm assuming I'd either have to track down YC's public key (where?) to add them as a petname, or transitively reach them via some other user that I trust.
Presumably you'd type something like `news.ycombinator.com.network-solutions.gnu`, since right now you are (ultimately) trusting Network Solutions to Do the Right Thing.
If you have a website running under a server with a name in your GNS domain and you want to link to a server with the name 'www' in a different GNS domain, you'd add a PKEY record for that GNS domain to your GNS domain (eg. called 'foo'). You can then link to https://www.foo.+/ and it will DTRT - someone browsing your site under the name www.jonathonw.gnu will resolve the link destination as www.foo.jonathonw.gnu.
Or share a name with another user?
If you want to share a link with someone I guess you'd share the .zkey version.
A greasemonkey type script might also be able to apply the right fixups.
Look this chapter in this document :
> 3.3 Relative Names for Transitivity of Delegations
> Users can delegate control over a subdomain to another user’s zone by indicating this in a new record
https://gnunet.org/sites/default/files/paper_cans2014_camera...
If names aren't fixed, how do you (for example) link from one website to another? Or share a name with another user?
One of the advantages of the public DNS system, with unique, canonical names, is that the same name should mean the same thing to everyone.