News for hackers. Stuff that matters.
Re:Introducing Tent - the decentralized social web by icebraining on Wednesday August 22, 2012 @05:05PM (#4419574)
A DNS requires people to agree about who owns a certain identifier, which would be problematic in a decentralized system (though there are proposals like namecoin).

I think a better system could be publishing a triple (name, keyfingerprint, current-server) on a shared datastore (e.g. DHT). The user doing the search would still need to find some out-of-protocol way to identify the right person, though.

EDIT: Kadmelia on Emule is a working implementation of a similar system to what I described, but for files instead of users.

Re:Introducing Tent - the decentralized social web by exact-ly on Thursday August 23, 2012 @12:33AM (#4420907)
Yes. The "keyfingerprint" might be the server's public key for purposes of end-to-end security of the connection. (No more SSL! There's better libraries now.)

cjdns has a simple approach: your tcp6 address is your public key. This the right idea. Leverage what you already have that is unique (not to imply IP address is necessarily truly unique, e.g., anycast).

But in general to be on the network, you have to at least one unique item: your network address. So leverage that to make other unique identifiers.

To encrypt communications, you may need to maintin encryption keys. So leverage them to be part of each peer's unique identifier on the network.

Connecting to strangers, and only using the network to get each and every bit of infromation from the outside world, is all fine and good, but this sort of peer-to-peer networking is much more valuable with peers who you can identify in person. Without using a computer. You can exchange all the above numbers (identifiers) on business cards.

Re:Introducing Tent - the decentralized social web by icebraining on Thursday August 23, 2012 @05:40AM (#4421580)
Personally, I don't like the network address as id, for two reasons; firstly, you don't control it, your network provider does (whoever that is - the server or ISP does). So if that entity wants, they can boot you off and pretend to be you.

Secondly, it ties you to them; what happens if you switch servers, or ISP, or whatever? I mean, right now I'm planning on switching to a cheaper, faster offer from another ISP, but I wouldn't do it if I were to lose all access to my accounts on the different services.

I think the id should be both controlled by the user and portable; that mostly leaves public keys and their fingerprints as ids.

Re:Introducing Tent - the decentralized social web by gizzlon on Thursday August 23, 2012 @06:44AM (#4421725)
So if that entity wants, they can boot you off and pretend to be you.

They could shut you down, but I don't think they could pretend to be you since they don't have your private key..

Re:Introducing Tent - the decentralized social web by icebraining on Thursday August 23, 2012 @06:53AM (#4421751)
That's my point; it's why I prefer public/private keys as ids instead of network addresses.
Re:Introducing Tent - the decentralized social web by yesbabyyes on Wednesday August 22, 2012 @06:50PM (#4420060)
Telehash would be pretty for the messaging, too. ;)

http://telehash.org

Re:Introducing Tent - the decentralized social web by nmcfarl on Wednesday August 22, 2012 @11:35PM (#4420759)
Telehash discussion here: http://news.ycombinator.com/item?id=4420634 - hopefully :)