Re:Dat: A P2P hypermedia protocol with public-key-addressed ...
by ignoramous on Saturday April 18, 2020 @08:18PM
(#22912288)
Thanks. Has anyone by any chance benchmarked hypertrie against u/marknadal's [0] gun.js?
Speaking of which, the gun.js network hosts the internet-archive (archive.org) [1] which is likely to be bigger than the English Wikipedia (?). Cloudflare runs an IPFS gateway. Are there organizations of similar size dat is looking to onboard or has onboard-ed?
---
A few questions:
1a. Re: hole-punching: Do you support clients on LTE (or, networks behind CG-NAT)? Is hole-punching just for the DHT connections (which seems to operate over UDP4) or for Feed (hypercore) connections, too (which default to TCP?).
1b. Are there plans to use WebRTC (like WebTorrent) instead of TCP or UDP sockets?
1c. In case of TURN relays, how long do you intend to support traffic through your servers? It might get cost-prohibitive at some point. Are (will) TURN relays (be) deployed worldwide to combat latencies?
2. Are hyperswarm and hyperdrive different example usages for hypercore or are they complementary? If so, how are those projects related, as in, is hyperdrive built on top of hyperswarm?
3. The project is spread across disparate GitHub accounts-- Some top-level packages in mafintosh's account and some in hyperswarm's, for instance. Is this intentional?
4. I saw references to merkle-trees, flat-trees, kademlia, HAMT, bitfields... is there a documentation on why these data structures are used? I can guess kademlia is for the DHT and merkle-trees for some form of entropy management. Are such implementation details documented (looking for something similar to gun.js [2] or redis [3] docs)?
5a. Can you please point out a few major differences to gun.js and ProtocolLab's IPFS?
5b. Conversely, what are some use-cases for which dat really outshines other such protocols?
Speaking of which, the gun.js network hosts the internet-archive (archive.org) [1] which is likely to be bigger than the English Wikipedia (?). Cloudflare runs an IPFS gateway. Are there organizations of similar size dat is looking to onboard or has onboard-ed?
---
A few questions:
1a. Re: hole-punching: Do you support clients on LTE (or, networks behind CG-NAT)? Is hole-punching just for the DHT connections (which seems to operate over UDP4) or for Feed (hypercore) connections, too (which default to TCP?).
1b. Are there plans to use WebRTC (like WebTorrent) instead of TCP or UDP sockets?
1c. In case of TURN relays, how long do you intend to support traffic through your servers? It might get cost-prohibitive at some point. Are (will) TURN relays (be) deployed worldwide to combat latencies?
2. Are hyperswarm and hyperdrive different example usages for hypercore or are they complementary? If so, how are those projects related, as in, is hyperdrive built on top of hyperswarm?
3. The project is spread across disparate GitHub accounts-- Some top-level packages in mafintosh's account and some in hyperswarm's, for instance. Is this intentional?
4. I saw references to merkle-trees, flat-trees, kademlia, HAMT, bitfields... is there a documentation on why these data structures are used? I can guess kademlia is for the DHT and merkle-trees for some form of entropy management. Are such implementation details documented (looking for something similar to gun.js [2] or redis [3] docs)?
5a. Can you please point out a few major differences to gun.js and ProtocolLab's IPFS?
5b. Conversely, what are some use-cases for which dat really outshines other such protocols?
[0] https://news.ycombinator.com/item?id=15818856
[1] https://news.ycombinator.com/item?id=17685682
[2] https://gun.eco/docs/RAD
[3] https://news.ycombinator.com/item?id=15384396