Like the top speed I’m getting is 6 KB/s from libgen and zlibrary. And downloads fail midway. And they didn’t provide torrent download for single books. Any recommended place to torrent books?
Like the top speed I’m getting is 6 KB/s from libgen and zlibrary. And downloads fail midway. And they didn’t provide torrent download for single books. Any recommended place to torrent books?
IPFS is tricky, but can be made to work, at least at Libgen scale. Content discoverability is always a problem, so depends on the number of pins on the network.
Content discovery on IPFS is complicated as you cant update information (it makes a whole new key, which has to be discovered).
Which is not a problem for tens to hundres of terabytes of library documents, which are all static. And there’s https://docs.ipfs.tech/concepts/ipns/ and https://docs.ipfs.tech/concepts/dnslink/ but latter suffers the same problems as DNS.
True, until you need to move them. It’s really a cat chasing it’s tail problem IMO.
Do you use IPFS? Thanks for the links btw, I do know how the underlying tech works, thats why I think it’s nice but lacking. It’s like the grand-pa protocol for decentralised content. Better contenders exist, but I see no or very little use of any, IPFS included, which IMO is a shame.
If you need to move the document bulk, you can either rsync the docs and repin them, or use IPFS native means of replication to remote – haven’t used those.
LibGen on IPFS used to work, try e.g. https://bafybeifaxsen4np54stc43phpnn3rh2crxie34d74yki43dultrh4vglqy/ – but I have no idea about how much of the library corpus is pinned currently.
For me, except that it’s kind of complicated to set up, this is what is missing with IPFS, the repin (or “cid” stuff IIRC) is breaking the decentralised part. It’s “almost” decentralised, but not quite.
Tenfingers is fully decentralised (it’s also very rugged against takedowns), you can just update the data without the need to change or regenerate the link, but it doesn’t work well with large datasets (a GB is already on the big side).
For me, a mix of them would be the best of worlds, large data that doesnt change: IPFS, small data that changes: Tenfingers, Large data that changes: IPFS links shared with Tenfingers (so that you can publish the new IPFS links easily).
I have approached IPFS users, but many doesn’t think it’s a problem that needs a solution.
What do you think?