How do websites like Anna's archive hide their hosting infrastructure? (discuss.tchncs.de)

submitted 9 hours ago by Bomnam@discuss.tchncs.de to c/piracy@lemmy.dbzer0.com

19 comments fedilink hide all child comments

With how many lawsuits they get and the total amounts they now have technically lost in court, how is it possible they still hide their hosting infrastructure? Anna's archive hosts a truly monumental amount of content and its not like its exactly easy to host petabytes(?) of content in secret easily. Hell the orders for hard drives should make it easy to find them. It's not like they can just tuck a raspberry pi with an Ethernet connection somewhere and throw up a proxy and call it a day. What kind of techniques are required to hide that amount of infrastructure? Especially under such scrutiny as the US government and many publishers coming for their throats I can't imagine it's a small feat.

you are viewing a single comment's thread
view the rest of the comments

[-] fonix232@fedia.io 26 points 8 hours ago

They also have all the data in a set of torrent files.

I've actually been working on an AA client + Readarr (yes yes I know the main project is dead, I meant for generally book-related Arr stack projects) provider.

The idea is pretty straightforward:

the client connects to the current AA instance and grabs the torrents
each torrent is added to a built-in client, with all files set to "don't download" (so at the moment it does nothing beyond peer discovery)
each torrent is now versioned and provides a metadata batch of all files and paths included
metadata is matched to paths during lookup
provider interface allows upstream software (e.g. Readarr, Chaptarr, etc.) to search for a specific release with some extra parameters (language, format, date added, etc.), uses AA approach of hash to path matching
path is matched to torrent, within that torrent, that path is set to be downloaded
upon download the file path is softlinked to destination provided for download
upstream picks up new file and parses it (then it gets passed to CWA, AudioBookShelf, Kavita or whatever other frontend you use)
the client also automatically selects 500MB worth of files with low availability. This 500MB is separate from what the user has actually downloaded, and is used to contribute back to the P2P net

[-] DebatableRaccoon@lemmy.ca 4 points 6 hours ago

This sounds awesome. I hope to be backgrounding it some day.

[-] FaceDeer@fedia.io 2 points 7 hours ago

This seems similar in general outline to Hyphanet, a system for distributed data storage that automatically handles random distribution and distributed searching. Unfortunately I don't think Anna's Archive puts its data on there, but perhaps you could consider having your client bridge to that and use it as an additional backup cache.

[-] UsefulIdiot@sh.itjust.works 2 points 8 hours ago

This is a cool as hell idea. I’m very interested. You have the code/ project up anywhere?

this post was submitted on 10 Jul 2026

55 points (98.2% liked)

Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

69771 readers

187 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others

Loot, Pillage, & Plunder

We heartily recommend visiting the free port of freemediaheckyeah (aka FMHY) while you sail the high seas, for all the freshest links the ocean has to offer.