@kaniini Is there a particular reason you choose Kademlia as a DHT?
Because due to its probabilistic properties I couldn't use it for my hashtag federation work and went with Chord instead.
Would be a shame if instances have to implement different DHTs if not absolutely necessary.
@kaniini my approach will definitively increase storage requirements, but hopefully not too badly as storage nodes just have to store the post IDs of some of the hashtags.
@kaniini What's problematic about the required storage structure in that regard?
@cjd @kaniini @abby Could you elaborate on why? I have my own suspicion of your answer: for content-addressed content, I think they're probably often fine, but if it's a "varying bucket" full of content, it's easier to intentionally drop content from it.
BTW, for the mutable datashards component (which I think Pleroma probably wants for moveable actor profiles) my suspicion is that a gossip network may be more useful than a DHT for informing about updates. Not sure about immutable chunks tho
@cwebber @kaniini @abby
I wrote a modified version of kademlia (it had an additional constraint) and I also ended up knowing a few of the bittorrent people. My opinion of bittorrent DHT is it's mostly a mouse that roars.
When you put data in the DHT, it gets pulled back to a real tracker by DHT scrapers and the same DHT scrapers are in there answering your requests. BUT it's Just Decentralized Enough to be opaque to the lawyers. @astro what's your opinion?
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!