Young entrepreneur in progress.
We can do one better than a customized version of a web browser. Why not create a local proxy like Tor to handle the DHT stuff? Looks like Dijjer is really close; all they need to do is provide an HTTP Proxy that can be put in the browser’s settings once.
Then, all URLs would be handled by this localhost proxy, taking advantage of the DHT technologies provided.
Once we get sites to support the additional headers to provide the client with a Jabber/XMPP address to negotiate updates with and a key to concurrently download the data via a distributed hash table, we’ll need a browser and subscriber that support them.
Possibly a modified version of Firefox, the nuWeb Browser would take advantages of these two headers in various ways.
I’ve been recently referring to Distributed Hash Tabses, or DHTs (no relation to the chemical that balds heads) in my entries and on the nuWeb project. Since I didn’t directly introduce them I’ll do so now.
Descriptions: * Wikipedia * infoAnarchy * nuWeb
A few weeks ago I finally began to understand how DHTs worked. Interestingly, they were different than what I thought they were. My goal for the DHT network for the nuWeb project is to provide put(data) and get(key) functions with the key being the hash of the data, whereas most DHT networks provide put(key,value) and get(key) functions where the hash is of the key and the data is arbitrary, quickly opening the possability of key collisions.
So, I began to feel at a loss. If DHTs don’t use the hash of the data and instead use the hash of the key, how could I use it for the P2P aspect of the nuWeb project? And then it hit me…
twitter del.icio.us