Damus
Technical Debt · 3d
DHT is not a silver bullet. Torrents get spam attacks, CJDNS routing tables have grown enough to require offloading the routing to dedicated nodes (this scaling problem inspired the creation of the ...
weev profile picture
> but discoverability of “unpopular” content is slower

Sure, but a social pinning model and IPFS peer graph makes this irrelevant. We’re not talking about an ancient file. We’re talking about a message that I *just posted* that is being ostensibly served by my followers. Your first IPFS node to check could be one I offer via the same tor onion as my relay. And I’m sure to have it, it’s my file. An easy place to query for a hash that is not me, in this instance, would be my followers, who are, in this hypothetical, pinning my content. You don’t need to search the entire IFPS network.

Regardless, this is a side channel. It doesn’t have to be a silver bullet! It just has to make my content more available than it already is, and reduce immediate stress during peak hours upon public relays and media servers.
1
Technical Debt · 3d
I don’t know the specifics that make IPFS slow, but I’m skeptical it’s something that could be fixed easily without some sort of hairy drawback (otherwise it would’ve been fixed upstream already). Your proposed solution would help offload blossom servers but not propagating notes themselves...