Live data from Hacker News

Libgen Storage Decentralization on IPFS

freeread.org

61–70 of 115 posts

Re: Libgen Storage Decentralization on IPFS

#62

The 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…

Am I understanding it right that DMCA takedown requests apply to a URL? 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.

In general DMCA takedown requests reference a URL to locate infringing content, but the actual requests ask that the content itself be removed and not just the URL.

Re: Libgen Storage Decentralization on IPFS

#63
post #43
post #39

Earlier quoted context omitted.

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…

IPFS is the engine of Filecoin, though. Filecoin just incentivizes IPFS nodes to store things. So further IPFS development should still be necessary from the perspective of making Filecoin development/adoption happen. (I say this, and yet I know it isn't true in practice. But why isn't it true?)

Pump up Filecoin price. Sell Filecoin. Move to Fiji. Don't do any coding while in Fiji

Re: Libgen Storage Decentralization on IPFS

#64
post #52

Earlier quoted context omitted.

> 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).

In the US the (very) common scenario is to get a couple warnings from your ISP and if you continue torrenting copyrighted material you will be dropped as a customer and banned.

> the (very) common scenario is to get a couple warnings from your ISP and if you continue torrenting copyrighted material you will be dropped as a customer and banned.

This is not "very" common - the ISPs don't really ban you, they just threaten you. I no longer do this, but I extensively torrented over multiple home ISPs and they would send me warnings but they would never actually do anything.

Re: Libgen Storage Decentralization on IPFS

#65

I'm hesitant to participate in IPFS in the context of libgen. Torrenting copyrighted materials (especially if you are distributing) can be quite expensive in some jurisdictions and I do not believe that IPFS is treated different than regular BitTorrent.

Check out https://gnunet.org/ It works well for file sharing as well. Don't know about copyrighted material though, have only shared my own files.

Does it actually work well? I tried to play with it a while back and while sharing files appeared to work, actually downloading them from other node didn't go that well..

Re: Libgen Storage Decentralization on IPFS

#66
post #38

Earlier quoted context omitted.

You're almost right. The IPFS gateway nodes also cache the content. IE, they are both storing, hosting, and sharing to other IPFS nodes.

how can one validate that the cached version is indeed bit equal to the one stored within ipfs?

You hash it, everything is content addressed.

Re: Libgen Storage Decentralization on IPFS

#67
post #38

Earlier quoted context omitted.

You're almost right. The IPFS gateway nodes also cache the content. IE, they are both storing, hosting, and sharing to other IPFS nodes.

how can one validate that the cached version is indeed bit equal to the one stored within ipfs?

The address of the file is the hash of the file. (Really the hash of the DAG of the file)

So you could validate it if you wanted to. Because the URL _is_ the hash, if you did validate it you could be very sure that it is correct.

If a webserver hosts a file, how can you be sure that file is correct? Sometimes the ship a sums file next to it. At best this can find corruption, but it would not find malicious files.

Re: Libgen Storage Decentralization on IPFS

#68
post #5

What'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…

See the comment above about Freenet, which does something like this; although according to https://freenetproject.org/pages/documentation.html#content it seems to prioritise popular files rather than rare ones.

IIRC eDonkey prioritised rare files, although I don't know if this was a property of the network or just a common choice in clients.

Re: Libgen Storage Decentralization on IPFS

#69
post #52

Earlier quoted context omitted.

In the US the (very) common scenario is to get a couple warnings from your ISP and if you continue torrenting copyrighted material you will be dropped as a customer and banned.

> the (very) common scenario is to get a couple warnings from your ISP and if you continue torrenting copyrighted material you will be dropped as a customer and banned. This is not "very" common - the ISPs don't really ban you, they just threaten you. I no longer do this, but I extensively torrented over multiple home ISPs and they would send me warnings but they would never actually do anything.

AT&T has banned a friend permanently so I would be careful about over-broad generalizations. Folks in my my household were torrenting and we got our service cut with the second offense until we went through some rigmarole promising we'd never do it again at which point they stopped. The cost to an ISP's lawyers to field these things isn't free and at least some really do respond with action.

Re: Libgen Storage Decentralization on IPFS

#70

A strange choice given that distributing copyrighted materials violates the IPFS Code of Conduct [0]. Why not use BitTorrent whose attitude toward copyright is much more in sync with libgen's? [0] https://github.com/ipfs/community/blob/master/code-of-conduc...

> distributing copyrighted materials violates the IPFS Code of Conduct

Even if so, what can they (the IPFS devs) even do about it?

Post reply on HN