News for hackers. Stuff that matters.

A comment on Beaker Browser and the Dat Protocol. Parent comment

Re:Beaker Browser and the Dat Protocol by eternityforest on Thursday September 05, 2024 @03:09AM (#41454301)
It seems like it was so much better designed than IPFS, since it had a native concept of collections instead of trying to make every block independently accessible on the DHT.
[ Parent | on HN ]
Re:Beaker Browser and the Dat Protocol by anacrolix on Friday September 06, 2024 @02:07AM (#41463326)
I'm glad others recognise this problem too.
[ Parent | on HN ]
Re:Beaker Browser and the Dat Protocol by immibis on Friday September 06, 2024 @07:55PM (#41470576)
IPFS doesn't try to. Only top-level directories are added to the DHT. To fetch a child object, your node asks the same node it got the parent from.
[ Parent | on HN ]
Re:Beaker Browser and the Dat Protocol by eternityforest on Monday September 09, 2024 @03:45PM (#41492717)
Did they finally change that? Last I checked the default settings was to spew every block on the DHT unless you use roots mode, and to dump your entire list of wanted blocks to all 500 or so connected peers you often have, just in case maybe they have a block you want.
[ Parent | on HN ]