does anyone know why libgen is still running over http? (But sincerely thanks for the site! it saved me on several occasions!)
Libgen Storage Decentralization on IPFS
41–50 of 115 posts
Re: Libgen Storage Decentralization on IPFS
#42Earlier quoted context omitted.
In my experience IPFS is only fast when you're using it through something like Cloudflare's IPFS proxy (which is basically a caching proxy). I haven't found IPFS to be actually usable any time I've tried running a node myself. Is that unusual?
This has been the state of IPFS for years now. The protocol and client haven't been developed to where they can work reliably in a real P2P scenario. IPFS only appears to work because most requests go strait to one of the big gateways which already has the content cached. Development of IPFS slowed to a crawl when most of Protocol Labs switched to working on Filecoin. It remains to be seen if either Filecoin or IPFS…
You can run the following in the console to see all your peers
for await (const peer of await node.swarm.peers()) { console.log(peer.addr.toString()) }
The console currently get's spammed pretty hard because they haven't implemented filtering out plain ws (non-wss) peers if you are connecting https. But it will use webrtc to find peers, and find all wss nodes in the network.Re: Libgen Storage Decentralization on IPFS
#43Earlier quoted context omitted.
In my experience IPFS is only fast when you're using it through something like Cloudflare's IPFS proxy (which is basically a caching proxy). I haven't found IPFS to be actually usable any time I've tried running a node myself. Is that unusual?
This has been the state of IPFS for years now. The protocol and client haven't been developed to where they can work reliably in a real P2P scenario. IPFS only appears to work because most requests go strait to one of the big gateways which already has the content cached. Development of IPFS slowed to a crawl when most of Protocol Labs switched to working on Filecoin. It remains to be seen if either Filecoin or IPFS…
(I say this, and yet I know it isn't true in practice. But why isn't it true?)
Re: Libgen Storage Decentralization on IPFS
#44Earlier quoted context omitted.
> Torrenting copyrighted materials (especially if you are distributing) can be quite expensive in some jurisdictions Why? Your ISP charges for BitTorrent traffic?
In case you are serious: Lawyer agencies are joining the swarm, recording IPs, write letters to ISPs and send you fines. That's very common for example in Germany. Edit: I didn't downvote you if it looks like that :)
And you have to pay the fines? That's nuts.
In the US, you are pretty much as likely to get fined for torrenting as you are to get arrested for jaywalking (although without the racial disparity).
Re: Libgen Storage Decentralization on IPFS
#45I think such materials should better be placed to darknets protecting the privacy of users and seeders, e.g., to I2P.
Re: Libgen Storage Decentralization on IPFS
#46The IPFS mirror really gives a substantial performance boost. In the past, the files had to be fetched from a tired server far away in Russia, the speed can be as low as 0.5 Mbps in my experience (depends on your ISP and connectivity), now it can be lightning fast thanks to P2P, 2 Mbps+, more than adequate to download a 100 MiB+ file. You don't even have to install IPFS (but you probably should, to maintain decentral…
Maybe IPFS can introduce a feature to generate one-time URLs, e.g. `oneTimeURL = f(realURL);`.
Websites then can generate new URLs for example every hour or even for each client request. Copyright bots will file a DMCA request to a URL which only they have.
Re: Libgen Storage Decentralization on IPFS
#47What's missing from this system(and P2P systems in general), is automatic pinning - i.e. the system automatically choses which files to pin on which user, to ensure every file is available on the net. It's a bit of tricky problem, because people may not like unknown, random files on their pc, and probably, because such algorithm is distributed and will need to resist attacks. But i think that the payoff is big: what…
If the pinning came with encryption where the key is not known to the pinned system, I think most would be OK with it. There's no way to know, or demonstrate that anyone could know, the contents of any given file. Furthermore, the file could be broken into encrypted chunks and distributed redundantly to many users. Kind of like BT turned inside out.
Re: Libgen Storage Decentralization on IPFS
#48Earlier quoted context omitted.
In case you are serious: Lawyer agencies are joining the swarm, recording IPs, write letters to ISPs and send you fines. That's very common for example in Germany. Edit: I didn't downvote you if it looks like that :)
> write letters to ISPs and send you fines. That's very common for example in Germany. And you have to pay the fines? That's nuts. In the US, you are pretty much as likely to get fined for torrenting as you are to get arrested for jaywalking (although without the racial disparity).
Yes, conveniently there's a second group of lawyers that focuses on getting people out of these fines...for a fee that's not so much lower. Unfortunately it's a bit of a business model in some countries.