Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> A trusted source of accurate information is a prerequisite for entering someone's information into a rolodex. This even a problem with actual rolodexes.

How do you get someone’s phone number today? You just ask them. I don’t see a problem with this.

If you’re interested in a more clever way to handle public names mapped to keys though, you should look at Iris[1]. Users are verified by web of trust. And information stays up to date because you’re actually connected with them in the web.

[1]: https://github.com/irislib/iris-messenger



> How do you get someone’s phone number today? You just ask them.

There's a lot of subtle assumptions in this. When you ask for someone's phone number, you are already communicating with them in another manner. Much of the trust in this is derived from that other communication channel.

For example, when I walk into a building that says "H&R Block" on the side of it, I know that the time and money spent into establishing a business with a legitimate appearance, is a significant barrier to say, a scammer. I can be somewhat assured that the person inside, if asked, will give me a phone number of someone who is actually capable of doing my taxes.

A situation where trust cannot be assumed is more like a phone number written on the wall of a bathroom stall at a rest stop: "call 555-5555, I'll do your taxes".


I shared Iris in my last comment but perhaps this would have been better to share to explain the idea.

I think what you’re looking for is the solution to indexes. You’re right that indexes are really the big issue here. We were talking about two different use cases but I get you now.

https://www.hackernoon.com/what-is-wrong-with-the-internet-a...

Of course, something ENS domains is another solution (per my original comment up the chain). But that also is price prohibitive and sort of annoying in its own way. The cost upholds current power structures, but many don’t have an issue with that.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: