Well if there's any upside to the .org fiasco it's that more people are realizing how corrupt the DNS + SSL CA cartel is

@cwebber I'd love for the Internet to get rid of the DNS system and use something better, less of a single-hierarchy-for-all and less artificial scarcity and squeezing out money from everyone.

An important part of that would probably be pet names.

@liw @cwebber For petnames to work I assume that everyone would need some kind of unique identifier, perhaps on a DHT. Waiting for everyone to have global static ipv6 addresses probably isn't going to be practical.

Thing is... Namecoin will not catch on. Only .com will likely resist...

@andreasio Namecoin has many of the problems DNS does.

Petnames or bust!

@cwebber @andreasio is there a good system or resource for Petnames that you can recommend? First I’ve heard of it and I’m curious

@dpwiz @phred @andreasio I've tried looking at GNS before and I'm not sure it's a correctly implemented PetName system, but I might be wrong.

By trying to be semi-compatible with DNS, it might break itself. That makes sense for .onion, where things are still universal; don't think it makes sense for .gnu, where naming local. But admittedly I haven't actually tried GNS.

@cwebber @phred @andreasio They abolished .gnu "treaty" since it was never ratified by the ICANN side and by now it's okay to put anything under any "TLD".

Please elaborate on self-breakage and petnames correctness :blobcat:

@dpwiz @phred @andreasio Hyperlinks are a good example; if you and I have different bob.gnu, and I link <a href="https://bob.gnu/">Bob's webpage</a>, obviously that won't be correct. My understanding is that gnunet users are encouraged to use a proxy that rewrites every page (?), but that seems alarming and error-prone to me.

@dpwiz @phred @andreasio
Instead I think the client should use the cryptographic identifier as all the hyperlinks but hide it in the interface with the petname. Similar thing happens with phone numbers and your contact list: the network doesn't know that 555 555-8519 is "Mom" on your phone, but your phone knows how to translate it for you. Similar with <blahblahblah>.onion translated in the *interface* to "bob's website"

@cwebber @phred @andreasio Yep. The protocol part is there. You can put URLs to names in PKEY "zone" which is http://www.5775456764467...56755.
Now, the browser have to look it up in the petnames cache, local zones, HELO records, etc.

@cwebber @phred @andreasio the thing that bothers me is key rotation, aliasing and management in general. Either you deal with content addressable storage and versioning, or PKI. And then there's OCaps to add to the mess...

Maybe we should utilize all three to build a sensible story for hyperlinked stuff. Which are certainly the "do more" idea that can't be reasonably dismissed.

@dpwiz @cwebber @andreasio have y’all seen go/ links? In my experience this solves naming in a local community, within a trusted group

obv letting anyone create or edit won’t work at scale, but in practice being able to bind words and URLs is an incredible tool

@phred @cwebber @andreasio My, they do have a lot of identical tracked links to their site... The SEO is strong with this one.

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!