News for hackers. Stuff that matters.
Re:GNU name system by JonathonW on Friday May 06, 2016 @02:04AM (#11642014)
> A petname is a name that can be freely chosen by the user. This results in non-unique name-value mappings as www.bob.gnu to one user might be www.friend.gnu for someone else.

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.

Re:GNU name system by geocar on Friday May 06, 2016 @02:38AM (#11642119)
GNUnet has canonical names as well: Files can be located by their content hash (e.g. gnunet://fs/chk/...) or by the signature of the peer offering the data (gnunet://fs/loc/...)[1]

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...

Re:GNU name system by gcb0 on Friday May 06, 2016 @03:54AM (#11642399)
the top linked page is the worst introduction to GNS ever. Those are much better.
Re:GNU name system by joveian on Friday May 06, 2016 @04:32AM (#11642505)
Yeah, gnunet.org wins the single highest coolness factor to website quality ratio in my opinion (they have other projects besides GNS that are even less well documented), although there is stiff competition. Here is a short paper on GNS: https://gnunet.org/sites/default/files/paper_cans2014_camera...

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).

Re:GNU name system by smilliken on Friday May 06, 2016 @02:48AM (#11642160)
A public DNS with unique canonical names would be nice, but we don't have one of those. The DNS we actually have is inconsistent for several reasons: replication lag, ownership disputes, legal and political disputes (governments disagree what content is ok), VPNs with custom entries, firewalls, host files, etc, etc.

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.

Re:GNU name system by apichat on Friday May 06, 2016 @05:58AM (#11642786)
Universal unique canonical names are not a good thing because the problem of name squatting exists.

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

Re:GNU name system by zeveb on Friday May 06, 2016 @12:24PM (#11644983)
> Universal unique canonical names are not a good thing because the problem of name squatting exists.

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.

Re:GNU name system by apichat on Friday May 06, 2016 @12:57PM (#11645185)
I agree.
Re:GNU name system by vog on Friday May 06, 2016 @03:54AM (#11642397)
Take this idea one step further, and you have IPFS, which is a very promising approach:

https://ipfs.io/

Re:GNU name system by chris_wot on Friday May 06, 2016 @07:13AM (#11643066)
I tried to setup ipfs on El Capitan yesterday. I stalked the OS X Homebrew FUSE package, mounted ipfs and it immediately fails complaining too many file descriptors are being used.

ipfs is awesome, but I want to first be able to mount it as the file system :-)

Re:GNU name system by matt_kantor on Friday May 06, 2016 @11:11AM (#11644489)
I haven't tried using IPFS, but the default ulimit setting on OS X is tragically low. You might want to try bumping it up.
Re:GNU name system by chris_wot on Friday May 06, 2016 @12:03PM (#11644841)
I tried - increased it to unlimited and it still had the same error :-(

I have zero knowledge of Go, so not even sure how to start troubleshooting.

Re:GNU name system by fiatjaf on Friday May 06, 2016 @10:18AM (#11644126)
IPFS is certainly not this idea taken one step further. It is a totally different thing.
Re:GNU name system by chilicuil on Friday May 06, 2016 @10:57AM (#11644399)
If we're talking about linking names to resources, ipfs/ipns is not a different thing https://github.com/ipfs/examples/tree/master/examples/ipns
Re:GNU name system by nitrogen on Friday May 06, 2016 @04:05AM (#11642425)
A public DNS with unique canonical names would be nice, but we don't have one of those.

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

Re:GNU name system by JonathonW on Friday May 06, 2016 @11:48AM (#11644741)
That's why I said "should" and not "does".

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.

Re:GNU name system by zeveb on Friday May 06, 2016 @12:20PM (#11644955)
> 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.

Re:GNU name system by pklausler on Friday May 06, 2016 @12:45PM (#11645113)
Distinct, not unique.
Re:GNU name system by caf on Friday May 06, 2016 @07:54AM (#11643274)
If names aren't fixed, how do you (for example) link from one website to another?

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.

Re:GNU name system by JonathonW on Friday May 06, 2016 @11:40AM (#11644682)
I'm presuming that means I'd need a GNUnet-aware browser? AFAIK, a normal browser doesn't send enough context when resolving names for the resolver to figure out that someone means www.foo.jonathonw.gnu if they pass it www.foo.+ and have been browsing www.jonathonw.gnu.
Re:GNU name system by caf on Sunday May 08, 2016 @07:51AM (#11653637)
Yes, or I believe the GNSProxy ( https://gnunet.org/book/export/html/1769 ) is an alternative.

A greasemonkey type script might also be able to apply the right fixups.

Re:GNU name system by apichat on Friday May 06, 2016 @05:07AM (#11642621)
Name registries still exist in GNS and they are still usefull but anyone can be a registry for anybody. So in a cultural context where a registry is mainstream, names are almost unique. But registries became contestable, you can avoid them and we have to require them to be libre, open source, and forkable.

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...

Re:GNU name system by fiatjaf on Friday May 06, 2016 @05:37AM (#11642721)
Read the thing to the bottom before criticizing. If you wanna share something for the long-run future you can use the canonical name.