Earlier quoted context omitted.
It still amazes me that 77TB is considered "small". Isn't that still in the $500-$1,000 range of non-redundant storage? Or if hosted on AWS, isn't that almost $1,900 a month if no one accesses it? I know it's not Big Data(tm) big data, but it is a lot of data for something that can generate no revenue.
> Isn't that still in the $500-$1,000 range of non-redundant storage? Sure. Let's add redundancy and bump by an order of magnitude to give some headroom -- $5-10k is a totally reasonable amount to fundraise for this sort of application. If it were legal, I'm sure any number of universities would happily shoulder that cost. It's miniscule compared to what they're paying Elsevier each year.
How to circumvent Sci-Hub ISP block
91–100 of 196 posts
Re: How to circumvent Sci-Hub ISP block
#92By the way, Sci-Hub has stopped adding new articles to the database for a few months now (background: https://www.reddit.com/r/scihub/comments/mk46x4/scihub_v_els... ). It would be great to develop a truly decentralised solution. Having a database of individual torrent links for each paper might be a start.
IPFS seems like a perfect fit for this and some of the scihub torrents are already in IPFS, but it's not an anonymous network. IPFS via the DHT tells the network of your whole network topology, including internal address you may have, and VPN endpoints too. It's all public by design as they don't want to associate IPFS with piracy per one of their developers. this thread has some discussions on the alternatives https…
Re: How to circumvent Sci-Hub ISP block
#93Earlier quoted context omitted.
There was that project some guy posted a while back that used a combination of sqlite and partial downloads to enable searches on a database before it was downloaded all the way. If you can fit PDFs somewhere into that you'd be golden. Or just use IPFS I suppose.
IPFS would face a similar challenge as the “keep torrents seeded” problem mentioned by GP. Wouldn’t there be risk to peers who host the PDFs?
Re: How to circumvent Sci-Hub ISP block
#94Re: How to circumvent Sci-Hub ISP block
#95Re: How to circumvent Sci-Hub ISP block
#96By the way, Sci-Hub has stopped adding new articles to the database for a few months now (background: https://www.reddit.com/r/scihub/comments/mk46x4/scihub_v_els... ). It would be great to develop a truly decentralised solution. Having a database of individual torrent links for each paper might be a start.
IPFS seems like a perfect fit for this and some of the scihub torrents are already in IPFS, but it's not an anonymous network. IPFS via the DHT tells the network of your whole network topology, including internal address you may have, and VPN endpoints too. It's all public by design as they don't want to associate IPFS with piracy per one of their developers. this thread has some discussions on the alternatives https…
Re: How to circumvent Sci-Hub ISP block
#97Re: How to circumvent Sci-Hub ISP block
#98Earlier quoted context omitted.
There was that project some guy posted a while back that used a combination of sqlite and partial downloads to enable searches on a database before it was downloaded all the way. If you can fit PDFs somewhere into that you'd be golden. Or just use IPFS I suppose.
IPFS would face a similar challenge as the “keep torrents seeded” problem mentioned by GP. Wouldn’t there be risk to peers who host the PDFs?
Re: How to circumvent Sci-Hub ISP block
#99Earlier quoted context omitted.
IPFS would face a similar challenge as the “keep torrents seeded” problem mentioned by GP. Wouldn’t there be risk to peers who host the PDFs?
I sort of feel like there should be some way to use some kind of construct to get people to seed things so that others seed things for them, but I haven't seen that invented yet.
Re: How to circumvent Sci-Hub ISP block
#100Earlier quoted context omitted.
Works on BT broadband
Virgin says no. Interestingly I get this: Secure Connection Failed An error occurred during a connection to sci-hub.st. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG