Hey everyone! 📚 I’m excited to introduce Bookracy, an open-source shadow library dedicated to preserving and freely sharing knowledge. With a large and growing collection, Bookracy is (annoying) ad-free, non-profit, and lightning-fast ⚡—plus, it’s fully open-source and powered by a passionate community. Whether you're a reader, researcher, or developer, there’s a place for you here. Check out our Reddit, website, GitHub, and hop into our Discord to join the conversation and help grow this movement for open access! 🤝❤️
putting aside the obvious glowie talk someone else raised, you should really, really reconsider your opsec. And I mean, really. Using discord to communicate? And spamming Reddit, from a non-dedicated account, no less? Posting PII to justify downtimes? If this gets any traction at all, you're in deep shit. There's a good reason Anna is as anonymous as she is. Cat is out of the bag at this point, I'd recommend shutting it down. You could always continue developing the code for it, the frontend looks pretty good. But please, reconsider if you have the dedication and knowledge it takes to run a shadow library and not be caught.
Seriously, I though Lemmy users would be a little more aware of this stuff. I've seen people openly saying they want to assault federal agents and government property, and now this guy
I'd be more than a little interested to be pointed towards a guide, or even just a bullet point list, of good opsec considerations or tools for a project like this. I've got time and technical ability but don't spend a lot of time thinking about these concerns. The last thing I want is to cause myself trouble I'm not ready for, but I'd like to make a significant contribution to the community, so I want to prepare adequately.
Any guides or lists you can think of?
Becoming a provider (on any significant scale) should be treated like a second job, at least. If you want to go the silent route, you need to completely separate your daily life from the illegal stuff. Obvious stuff, like no shared email- or other accounts, but even down to no shared browser sessions. The old fashioned way is a second laptop. If you want to make an impact and contribute to the community, consider seeding torrents for some of the existing shadow libraries. Anna's Archive has about a petabyte of torrents that have less than three seeders, for example.
I can appreciate your concern and point of view, but I asked "so if I want to do this, how can I prepare to do it safely?" And your response was "just don't, do this instead." I can certainly seed, but that's not what I'm aiming for. I am far more interested in creating systems and providing content. My time is...flexible. Suffice to say, the time concern is not going to be the roadblock.
You're right, and I'm sorry if I came over as condescending. The thing is, with projects like these, you need to front load a lot of the safety concerns if you are going to be the one actually hosting the content. It'd be an easier entry to contribute to existing structures, staying more low-key and learning along the way. Many established projects are open-source and need programmers and hackers to help improve and secure their codebases, for example.
That said, if you wanted to start something of your own, I think Anna's blog is a nice starting point, before you delve into the technical nitty-gritty:
https://annas-archive.org/blog/blog-how-to-become-a-pirate-archivist.html
https://annas-archive.org/blog/how-to-run-a-shadow-library.html
Then, for the actual hosting process, much depends on the stack you use. Never pay for anything in a way that can be traced, which basically only leaves cash or anonymous crypto like Monero. Don't use any account names, emails, passwords, etc that you've ever used before. Never, ever go boasting to strangers, or even worse, friends, about what you're doing. Do all the standard things of hardening your servers, but always plan around some or all of them being shut down it seized. Even "bulletproof hosting" providers get raided every once in a while. That means decentralization, and don't put convenience over safety.
Now, while shadow libraries and other forms of media piracies certainly are sought-after targets, you're likely not going to be anyone's number one priority, while there's still rings of child abusers and terrorists on the web. But once you reach a certain size, state actors will come after you, like they did after z-lib a while ago. I don't have any comprehensive guides on Opsec (and I'm no expert on it, by any measure), but most of it boils down to common sense and keeping your mouth shut, anyways. Most people that get busted don't have missed some technical vulnerability, but because they've talked about their illegal projects on accounts linked to their real name, or something similarly trivial.
our model is just like the old movie-web, we are open source and if we are DMCA'd then we will take it down but our mirrors will still be up but i understand the opsec point and may move from discord to signal
that's good and all, but as it stands now, it seems almost guaranteed your PII will leak. Are you okay to never set foot into a country that extradites to the US again?
since its open source and the backend will be open source in the future (after i rewrite) i can still step away from the project and everything can be taken and hosted by a different person
that's not how it works. the code and website may live on, but you are committing a crime right now (nothing wrong with that). If law enforcement comes after you, it won't matter if you've 'stepped away' in the mean time. You can either go the route of Anna, keep very tight Opsec and make sure nothing seeps through the cracks. Or you go the way of Alexandra Elbakyan, make your piracy public, to make a point. That means you willingly accept never being able to travel anywhere that has enforced copyright laws. If you half-ass it somewhere in between, you will get caught, and you will face prison time or hefty fines (potentially millions). Are you aware of that?
Bookracy doesn’t exploit the copyrighted material for financial gain, unlike typical piracy websites that might sell access to pirated content or host popup / redirect ads for profit And for the part of me commiting a crime its always innocent until proven guilty - if it can be proven im storing the books fair play but weve taken precautions against that paying through crypto bulletproof servers ect
@[email protected] mentioned Alexandra Elbakyan. Do you know who that is? Aaron Schwartz ended up dead just for having a lot of journal articles and giving away a bunch of public domain materials.
Oh my.. You sound really unprepared for what you are getting into. There is no such thing as perfect security. And if someone sold you on that premise, you were tricked.
Even if your host is doing the absolute best job possible, your group can still screw it up any one of a million ways. Given the cavalier attitude here, that's going to be happening soon and happening often.
Honestly you sound like a total heat score..
The publishers don't care. They're suing LibGen, scihub, etc nonetheless. Non-commercialism will not protect you. Crypto can be very traceable, it's by definition an open ledger, and "bulletproof servers" is a term applied very broadly, often by dubious actors. Besides that, any Opsec is only as strong as the weakest link. You're running a second domain via Namecheap, for fucks sake! Don't take this lightly, this is not a game. A state actor could probably identify you within days. Are you ready for that?
the namecheap domain was bought using fake details on a paypal that had no card connected to it - but i understand which is why i bought a .ru domain from cheapprivacy.ru
Are you saying there is a way to escape my student loa*s forever?
My opsec doesn't allow for any Russian projects at all
having a .ru domain is just precaution against takedowns - none of the devs are russian its just the west and russia dont get along so takedown requests for a .ru domain would be ignored by russia
Fair, at least as long as they're not open-source