This is a thread to track which areas of the protocol need to be better defined / stabilized...
A documentation point: what is the logic to handle opens, the retransmits, changing keys, and handling the at timestamps.
The pull request for DHT handling, type:bucket: #18
The pull request for seek partials: #10
I'd like to add the sending-path information to the type:path packets (so the recipient knows what path the sender was sending to), this would replace getting the info implicitly from a type:seek see response (for yourself)
Standardize and document a common seeds.json format :)
Probably better and easier ways to bootstrap encrypted connections. Like fixed data to compare your output with. Could even be a test server or test DHT that returns debug info etc so it's easier to get the connectivity done
From @fd, document what happens when one hashname has multiple instances.
Prototype and document better https://github.com/telehash/telehash.org/blob/master/ext_pool.md for use as secondary/app-specific DHTs (also from @fd).
Perhaps document how to do seek logic better? (via @dvanduzer)
Most of these have been addressed by #22 so I'm going to close this as a tracking thread, we'll be doing another review soon and start a new issue to track that.