To be fair, Z-Library doesn't charge unless you want to download more than 10 books per 24 hour period. That's per account and although they ask you not to open multiple accounts they don't seem to do anything to stop you.
Pirate Library Mirror: Preserving 7TB of books (that are not in Libgen)
21–30 of 438 posts
Re: Pirate Library Mirror: Preserving 7TB of books (that are not in Libgen)
#22Earlier quoted context omitted.
Do you really want your ISP to know which piracy sites you frequent? This is all being sent in plain text. Or they could change the content, insert a redirect, or inject ads without your knowledge. TLS is needed on all websites - not just those with interaction.
They still know which sites you visit even with https.
only the destination IP. TLS encryption is inside tcp and around the http protocol.
Re: Pirate Library Mirror: Preserving 7TB of books (that are not in Libgen)
#23Earlier quoted context omitted.
https won't keep your ISP from knowing you visited the site. And the rest of those? For a text-only blog, they seem kinda trivial.
only the destination IP. TLS encryption is inside tcp and around the http protocol.
Until ESNI becomes mainstream (and browsers offer the ability to enforce it), the domain name is also sent out in plaintext.
Re: Pirate Library Mirror: Preserving 7TB of books (that are not in Libgen)
#24HTTP-only makes me weary of visiting a self-professed piracy site. They couldn't even spring for a Let's Encrypt cert?
Re: Pirate Library Mirror: Preserving 7TB of books (that are not in Libgen)
#25Earlier quoted context omitted.
Do you really want your ISP to know which piracy sites you frequent? This is all being sent in plain text. Or they could change the content, insert a redirect, or inject ads without your knowledge. TLS is needed on all websites - not just those with interaction.
https won't keep your ISP from knowing you visited the site. And the rest of those? For a text-only blog, they seem kinda trivial.
> https won't keep your ISP from knowing you visited the site
If you use DoH, yes it does. Unless I'm mistaken. They only know the IP address of the remote server.
Re: Pirate Library Mirror: Preserving 7TB of books (that are not in Libgen)
#26Earlier quoted context omitted.
They still know which sites you visit even with https.
only the destination IP. TLS encryption is inside tcp and around the http protocol.
You don’t need to copy and paste your reply everywhere it’s relevant on HN. Even us flea brains can carry your remarks in our head and apply them to similar comments.
Re: Pirate Library Mirror: Preserving 7TB of books (that are not in Libgen)
#27So, if I get it right. First there was Libgen, which is mirrorable. Then, some Z-Library copied Libgen and added some more books, without making it mirrorable. The goal is to make these new books, which are not mirrorable — mirrorable (i.e. to "preserve" them).
So, why not just re-upload them to Libgen, then? I guess somebody will do that now anyway, but you could easily done it in the first place, without making your own mirror, which is not a mirror of Libgen. Just upload them to Libgen and make a mirror of Libgen.
Re: Pirate Library Mirror: Preserving 7TB of books (that are not in Libgen)
#28Earlier quoted context omitted.
https won't keep your ISP from knowing you visited the site. And the rest of those? For a text-only blog, they seem kinda trivial.
> https won't keep your ISP from knowing you visited the site If you use DoH, yes it does. Unless I'm mistaken. They only know the IP address of the remote server.
And nobody would ever think of keeping a reverse DNS index.
Re: Pirate Library Mirror: Preserving 7TB of books (that are not in Libgen)
#29Re: Pirate Library Mirror: Preserving 7TB of books (that are not in Libgen)
#30HTTP-only makes me weary of visiting a self-professed piracy site. They couldn't even spring for a Let's Encrypt cert?
*wary
For some reason I'm seeing this mistake more and more lately. https://en.wiktionary.org/wiki/weary vs https://en.wiktionary.org/wiki/wary