So, yeah: Do you save your torrent files or delete them after you've added them to your favorite torrent client? Why? Not the underlying data, just the torrent files themselves.

I'm undecided. I figure if I save them and back them up to an offline/offsite device, then I can (mostly/hopefully) recover from hardware failure by simply re-adding all the torrent files to my favorite client. The downside is deciding how to organize them.

I'd love to hear from the community on this.

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

[–] stupid_asshole69@hexbear.net 6 points 4 days ago (1 children)

The client saves them.

If you have a lot of crap in small files it might be time to stop depending on the directory structure to navigate and switch to a database.

[–] Moxible@monyet.cc 1 points 2 days ago (2 children)

I'm struggling with this, could you point me in the right direction? what is a good organizing way/program?

[–] Mordikan@kbin.earth 1 points 22 hours ago

You could try something lightweight and easier like sqlite3. You don't have to have a full blown postgres or mysql server running that way. Just have your .db file and open it with the sqlite3 command. You still would have to learn basic SQL but nothing over the top especially if its only a few columns you're creating.

One fun thing you can do technically is store files inside the DB structure as base64 encoded values. So, you might have something like a unique ID, the name of the torrent, then the torrent itself all in one location. If nothing else, something fun to play around with.

[–] stupid_asshole69@hexbear.net 1 points 2 days ago

Choose a db you’re comfortable with, create structures in it that represent your files and their location in your filesystems, add more structures that represent metadata and then query it when you need to find things.

It’s what phones do.