I'm considering it for a future system to sidestep the cloudflare bs with the *arr stack. I dont want to use flarsolverr as it just moves the problem to a different place. We can change urls for now and indexers but long term cloudflare is a problem.

I've been looking into local dht database to address this.

Im curious to hear your experiences with bitmagnet , magnetico or if you are doing something else.

Do you clean the db to certain media types or only have actively seeded content ?

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

[–] Fedegenerate@lemmynsfw.com 1 points 4 hours ago

I don't do anything with it, pure set and forget. I probably should, I don't use nsfw as all that is under a different stack, different gluetun, and different network namespace. As for size, I don't know but I found this in the FAQ:

What are the system requirements for bitmagnet?

As a rough guide, you should allow around 300MB RAM for BitMagnet, and at least 1GB RAM for the Postgres database. You should allow roughly 80GB of disk space per 10 million torrents, which should suffice for several months of crawling, however there is no upper limit to how many torrents might ultimately be crawled. The database will run fastest when it has plenty of RAM and a fast disk, preferably a SSD.