Ludvig Lundgren

I think it's probably better to use their api to get the name than to download all torrents to parse. I'll try and get started on this soon.

That would be nice indeed.. Not an easy task to do properly tho. Will see what I can do. Putting it in the backlog of stuff.

Found this new library which could potentially be a good fit for this https://github.com/ssrathi/go-scrub

Hi @jmechnich! Thanks for making the Homebrew formula, very useful!! Is it updated manually with new versions or do I need to setup webhooks to trigger builds or similar? As...

Generated docs could be something, but it's not just that, there are other comments in the README etc. I've used [Docusaurus](https://docusaurus.io/) a lot and it's pretty powerful and works well...

Hey @Acamol , sorry for this taking so long to get back to. I made a change to use the built in filepath.join to build the path which should make...

Hi! Using hash or name prefix is not supported, you need to use the full hash. `qbt torrent remove --hashes="75439d....282" --delete-files --dry-run` I'll look into adding support for removing by...

Hi! It's not supported with that same method but you can do it manually by doing an `export` of the other client and then modify paths if needed before you...

Hi! That should work, but I need to debug with qbit 4.5.5 and check if there's any changes needed.

Hi! Sorry about the late reply. The current implementation (in v2.0.0+) can take either a torrent hash or filter by category and/or tags. Also not that it only runs "ad-hoc"...