4 ms·

I'm sorry, but accessibility and UX is a primary focus, and then you explain that urls consist of a gigantic hex string? I can't share a file without having to

I'm sorry, but accessibility and UX is a primary focus, and then you explain that urls consist of a gigantic hex string? I can't share a file without having to copy paste the url, and I can't look at two similar urls and immediately determine which is which. No thanks. This seems like yet another product that seems good on paper, and seems great if you're a nerd, but this will never catch on with the average consumer.

repolfx 7y ago
They don't usually. You can put the key in DNS and then use regular DNS names.
macawfish 7y ago
The keys are akin to IP addresses, which are also not so human friendly. People are still trying to wrap their heads around decentralized naming systems. There are lots of ideas, and nothing has stuck yet in a groundbreaking way. But yeah, the naming problem is independent of what this protocol gives us.
- rtkwe 7y ago
  I think the best idea for naming is probably going to be something like giphy or what3words (though their implementation could use work since they're not directly translatable between multiple languages) where a hex address gets encoded in N words which are generally easier for people to grok than N*m (m being 2/4/8 depending on how many hex characters are encoded in which words). Choosing the words is hard though especially as you add more languages.