Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How to circumvent Sci-Hub ISP block

fragile-credences.github.io

Post reply on HN
Print view View original

141–150 of 196 posts

Re: How to circumvent Sci-Hub ISP block

#141

Post by sneak »

MaxBarraclough wrote: post #108
sneak wrote: post #54

Another option is to simply configure your workstation to use DoH. Then your ISP can't fuck with your address resolution. I recommend using NextDNS, and then setting up a provisioning profile at https://apple.nextdns.io to set it as your revolver on your macs and ios devices. The ad-blocking features are a nice bonus, too. NextDNS also has a cool free software CLI local DoH proxy resolver which works a charm.

From the page's footnotes: > Changing your DNS resolver to a public one like Google’s instead of your ISP’s is not sufficient as of 2021, for two ISPs I’ve tested, and I suspect for all UK ISPs that implement blocking.

I read the article in full.

Changing your non-DoH resolver (such as using Google Public DNS) means requests and responses can still be edited by your ISP. This is what the article is talking about.

I suggested DoH (encrypted DNS) because this is not subject to such tampering. DoH (DNS-over-HTTPS) is not the same as traditional unencrypted port 53 DNS.

Really, anyone who gives a shit about privacy should be using DoH exclusively, otherwise you are basically uploading your web history in real-time to your ISP for mining and resale.

Re: How to circumvent Sci-Hub ISP block

#143

Post by BelenusMordred »

zolland wrote: post #98
divbzero wrote: post #70

Earlier 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?

What kind of risk?

IPFS is not anonymous and like other p2p protocols shares your ip address. People seeding articles would get legal notices just like torrents now.

There's been a bit of effort to get it working over tor for years now but the fundamental design makes this difficult. Also despite all the money that has poured into filecoin this doesn't seem to be a priority.

This issue is nearly 6 years old:

https://github.com/ipfs/notes/issues/37

Re: How to circumvent Sci-Hub ISP block

#144

Post by dredmorbius »

mandelken wrote: post #130
spicybright wrote: post #122

Earlier quoted context omitted.

Why map anything to words for strict identification? Words and language are very error prone vs an id number or hash.

Probably because for written text the words identify the content while the hash relates more to the digital carrier format (pdf vs epub) and id number can change between publications, countries, etc.

Bingo.

And to drag in metadata, it may:

- Not be present.

- Be inaccurately applied to the correct work (metadata say the work is different, work is in fact related/same).

- Be inaccurately applied to the wrong work (metadata say the works are the same/related, they are not).

Re: How to circumvent Sci-Hub ISP block

#145

Post by derefr »

tmkadamcz wrote: post #78
jandrese wrote: post #26

Earlier quoted context omitted.

Millions of individual torrents is not a great solution. Keeping them all seeded is basically impossible unless they run a seed for each one, at which point they might as well just host the files. Plus you'll never get the economy of scale that makes BitTorrent really shine. When you have a whole lot of tiny files that people will generally only want one or two of there isn't much better than a plain old website. A t…

There are already torrents of the archives. But supposing scihub was taken down it's pretty non trivial to get from the archive back to a working site with search functionality. For one thing, none of Sci-Hub's code is available.

Seems like what should be in each torrent is a virtual appliance preloaded with one shard of the data, where that virtual appliance has a pre-baked index for searching just that shard's data. Then one more torrent for a small search-coordinator appliance that fans your search query out to all N shard appliances.

Re: How to circumvent Sci-Hub ISP block

#146

Post by int_19h »

AlexandrB wrote: post #55

The way SciHub is being treated by governments is pretty infuriating. There's a tiny minority of people who have an interest in keeping SciHub off the internet, and they're generally neither the researchers who write the papers, nor those who want to read them. Despite this, the power of the state has been used repeatedly to keep SciHub inaccessible and limit their ability to get funding.

SciHub is just one instance of the broader problem, which is that governments - even ostensibly democratic ones - don't actually operate in the best interests of the governed.

Which, I think, shouldn't be surprising when our "representatives" ostensibly speak for hundreds of thousands (and sometimes, millions) of people each. True democracy requires a much shorter and more direct chain of responsibility.

Re: How to circumvent Sci-Hub ISP block

#147

Post by i5heu »

tmkadamcz wrote: post #10

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

This is where IPFS shines.

In fact, there is already a ipfs mirror of scihub.

Re: How to circumvent Sci-Hub ISP block

#148

Post by fnord77 »

dredmorbius wrote: post #83
jandrese wrote: post #26

Earlier quoted context omitted.

Millions of individual torrents is not a great solution. Keeping them all seeded is basically impossible unless they run a seed for each one, at which point they might as well just host the files. Plus you'll never get the economy of scale that makes BitTorrent really shine. When you have a whole lot of tiny files that people will generally only want one or two of there isn't much better than a plain old website. A t…

What documents (books, scientific articles) benefit from specifically is a number of highly consistent, highly accurate identifiers: DOI (scientific articles), ISBN (published books), and others (OCLC identifier, Library of Congress Catalogue Number, etc.) With the addition of hashsums (even MD5 ad SHA1, though longer and more robust hashsums are preferred), a pretty reliable archive of content can be made. It's a cu…

text to speech the doc then an acoustic fingerprint on the audio :)

Re: How to circumvent Sci-Hub ISP block

#149

Post by fabioyy »

jandrese wrote: post #26
tmkadamcz wrote: post #10

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

Millions of individual torrents is not a great solution. Keeping them all seeded is basically impossible unless they run a seed for each one, at which point they might as well just host the files. Plus you'll never get the economy of scale that makes BitTorrent really shine. When you have a whole lot of tiny files that people will generally only want one or two of there isn't much better than a plain old website. A t…

only if it was possible to use chia to store content.. it would be a game changer

Re: How to circumvent Sci-Hub ISP block

#150

Post by nextaccountic »

andyxor wrote: post #28
tmkadamcz wrote: post #10

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

So what? bittorrent is all public too. It hasn't prevented the piracy scene for making releases.

what ipfs here provides over torrent is the ability to add more files instead of creating new torrents

Post reply on HN