TeleHash

Not an expert, but TeleHash [1] might be a more lightweight alternative than freelan for a lot of applications. [1] https://github.com/quartzjer/TeleHash/blob/master/org/v2.md

Every time I mention this on HN, at least 15 people upvote it - which means they didn't know about it. So I feel obliged to repeat it again and again (as I usually use this method a few times every week and it's tremendously useful for me): If you want to get Google's cached version of a webpage, just type cache:[url] e.g.: cache:https://github.com/quartzjer/TeleHash/issues/5 in the search bar and press return.

I was just looking at this as something that could be combined with Tent. From what I've heard, the v1 docs are inadequate to develop a working implementation, and this draft for version 2 of the spec isn't done, and hasn't been updated in awhile: https://github.com/quartzjer/TeleHash/blob/master/org/v2.md My conclusion was that TeleHash is a cool concept, but not a solid foundation you can build something on just yet.

From the Wiki: [...]End: a SHA-1 hash key (40 hex characters, 160-bits) stored in the global DHT and distributed between switches. Switches will distribute and look up ends in the global DHT that are important to them. TeleHash defines the SHA-1 hash of the external IP:PORT of a switch as part of the protocol. Applications built on top of TeleHash can add their own ends to the DHT like hashes of files, hashes of e-mail addresses or hashes of other application-specific values (e.g. user@chat).[...] So if i understand this right, every packet has a protocol-defined +end and the application can add it's own end on top (i.e. an Email adress?). https://github.com/quartzjer/TeleHash/wiki/My-Understanding-...

There is some version 2.0 on its way: https://github.com/quartzjer/TeleHash/commit/14cecbb2e58dca4...

This wiki page got me much closer to understanding what's really going on here: https://github.com/quartzjer/TeleHash/wiki/My-Understanding-...

Might be for NAT traversal, ala something like: http://en.wikipedia.org/wiki/UDP_hole_punching One of the wiki pages (https://github.com/quartzjer/TeleHash/wiki/My-Understanding-...) specifically talks about working with NAT: "Packets can continue to pass through NAT network devices like home routers"

This wiki page seems a little clearer, though anything prefaced with "My Understanding" might be a little suspect. https://github.com/quartzjer/TeleHash/wiki/My-Understanding-... So my understanding of that is that TeleHash is something of a cross between BitTorrent and Tor. Theoretically it allows for a totally distributed Internet. Though it looks like the implementation is rough, so it's hard to say how well-defined the protocol is.