91–100 of 151 posts
Why the hell is this site not https? Note the first blog post was in 2022. No https in 2022? Red flag. This looks like a honeypot to me And for the record, z library gets its books from libgen? Correct me if I'm wrong, but it was just a frontend?
Why the hell is this site not https? Note the first blog post was in 2022. No https in 2022? Red flag. This looks like a honeypot to me And for the record, z library gets its books from libgen? Correct me if I'm wrong, but it was just a frontend?
How does TLS vs No TLS weight in on your suspicious if something is a honeypot or not? It's as trivial for three-letter agencies/black hats to setup as for trusty individuals/corporations.
Earlier quoted context omitted.
Copying is not stealing. Stealing removes the original, copying leaves the original intact.
let's just be adults here and face it. unless using rhetoric, we still dont know how to deal with piracy in 2022
In terms of amount-of-benefit, the second vastly outweighs the first.
But if the author can't pay his bills then there is no author.
Does that cover it?
Would UBI fix this?
Why the hell is this site not https? Note the first blog post was in 2022. No https in 2022? Red flag. This looks like a honeypot to me And for the record, z library gets its books from libgen? Correct me if I'm wrong, but it was just a frontend?
> Why the hell is this site not https? This looks like a honeypot to me How does TLS vs No TLS weight in on your suspicious if something is a honeypot or not? It's as trivial for three-letter agencies/black hats to setup as for trusty individuals/corporations.
Keep in mind, the first post on this site was in 2022. 2022, and no https... is this some kind of joke?
And in this case the adversary isn't necessarily the three letters, it's the copyright holders and legal system. No https makes ISP logs even more useful
Instructions are not easy. I want a out of the box solution to help without having to deeply dig into the internals. Something like archive team warriors: http://warrior.archiveteam.org/ For example, > Bitswap vs DHT I don't care. I want to help without having to care about these details. > Launch one or multiple IPFS servers (see previous blog post; we currently use 4 servers in Docker). what? how? where? link? no o…
Earlier quoted context omitted.
> Why the hell is this site not https? This looks like a honeypot to me How does TLS vs No TLS weight in on your suspicious if something is a honeypot or not? It's as trivial for three-letter agencies/black hats to setup as for trusty individuals/corporations.
We're talking about seeding a library full of copyrighted content. The person who made this site couldn't take 2 seconds to set up HTTPS? They're either incompetent or part of a honeypot. In either case, it's best to steer clear Keep in mind, the first post on this site was in 2022. 2022, and no https... is this some kind of joke? And in this case the adversary isn't necessarily the three letters, it's the copyright…
Instructions are not easy. I want a out of the box solution to help without having to deeply dig into the internals. Something like archive team warriors: http://warrior.archiveteam.org/ For example, > Bitswap vs DHT I don't care. I want to help without having to care about these details. > Launch one or multiple IPFS servers (see previous blog post; we currently use 4 servers in Docker). what? how? where? link? no o…
From the article: > If this is all too involved for you, or you only want to seed a small subset of the data, then it might be easier to pin a few directories: 1. Use a VPN. 2. Install an IPFS client. 3. Google the “Pirate Library Mirror”, go to “The Z-Library Collection”, and find a list of directory CIDs at the bottom of the page. 4. Pin one or more of these CIDs. It will automatically start downloading and seeding…
The best instructions can have descirptions, but also contains a FULL list of command lines instructions, ideally without any placeholders.
Why the hell is this site not https? Note the first blog post was in 2022. No https in 2022? Red flag. This looks like a honeypot to me And for the record, z library gets its books from libgen? Correct me if I'm wrong, but it was just a frontend?
Also, consider your risks more holistically:
* Honeypots can and do have valid https certificates, what matters is who controls the site (for example, when the FBI took over a kiddie porn site, it changed the site to deliver over https a zero-day exploit for Tor Browser that broke out of the browser sandbox and deanonymised the visitor) * Eavesdroppers can tell you visited a specific HTTPS site by looking at your TLS1.2 SNI in cleartext. Even if you're using TLS1.3 (which fixes that leak, but is currently up to the browser/site to negotiate), eavesdroppers can still correlate site access with your DNS requests. Even if you use DNS-over-HTTPS/TLS, you don't know if your DNS provider is in cahoots with the eavesdropper. You have to trust someone
Where your actual risks lie in visiting an HTTP-only site:
* If the site has forms/cookies, an eavesdropper can see them. In this case, https buys you nothing; your concern is that someone can tell if you visited this site once, not that they can tell you're a repeat visitor * Eavesdroppers can see any headers that your browser hands out (mainly user-agent) that could more granuarly identify you vs just your IP address * Active attackers with the ability to control your traffic can place anything they want on the website by spoofing its responses. With https they could only deny you access to the site
The benefits of HTTPS over HTTP are enormous, but you have to understand what its limits are. If you're concerned about web surveillance, you should be something like Tor Browser to visit websites, and understand that even it has limitations.
I just wonder why all that can't be uploaded into Library Genesis? They already have the distribution part sorted out (IPFS, Torrent, even ed2k!).
Most of it probably is on libgen. Putting all the eggs into one basket doesn't seem like a good move when booksharing sites keep getting shut down.
Earlier quoted context omitted.
From the article: > If this is all too involved for you, or you only want to seed a small subset of the data, then it might be easier to pin a few directories: 1. Use a VPN. 2. Install an IPFS client. 3. Google the “Pirate Library Mirror”, go to “The Z-Library Collection”, and find a list of directory CIDs at the bottom of the page. 4. Pin one or more of these CIDs. It will automatically start downloading and seeding…
Any instruction that involves "Google X" (or even a general term "Install Y"), is not a good instruction. It is like a maze - easy to go once you know the path. Otherwise - dozens of subtle things that can go wrong, at each step (e.g. installing a different version of Y, or to a wrong path, etc). The best instructions can have descirptions, but also contains a FULL list of command lines instructions, ideally without…