I suggest adding the following to Settings.toml such at a query like

magnetfinder --all --depth 10 --show 100 -q "arch linux iso" can be reduced to
magnetfinder "arch linux iso"

• piratebay = "true"
• nyaa = "true"
• yts = "true"
• depth = 10
• show = 100
• proxy = "some_proxy_value"

I figure I can do all this with aliases, but it would be nice to have it as part of the config.

> magnetfinder -aq 'asdklasdklasdklasdksadlkasdlksaldkasldkasldkasdasdkasldkasld'
Error getting downloads directory, falling back to home directory
╭───┬──────┬──────┬───────╮
│ # ┆ Name ┆ Size ┆ Seeds │
╞═══╪══════╪══════╪═══════╡
╰───┴──────┴──────┴───────╯
Type 'n' to display 20 more torrents, or select torrent(s) by #:

It should not be interactive if no results are returned.

> magnetfinder -aq 'big buck bunny'
Error getting downloads directory, falling back to home directory

I want to use this programatically to grab magnet links for specfic matches

The following bash code does not provide the prompt, causing it to just hang

m="$(magnetfinder -aq 'big buck bunny')"

Everything besides the magnet result should be outputted to /dev/tty or /dev/stderr instead of stdout. Perhaps https://docs.rs/ttyecho/0.1.2/ttyecho/ will help.

That said, providing #8 will work around this.

I was checking out crates that relate to searching torrents and apparently magnetfinder is leagues ahead of everything else. I especially like that it's available as a binary since this allows for easy interoperability from programs in other languages, and I do think this is much better than having only library bindings, however I believe it would be a lot better to have the option of using it as a library when programming in Rust, especially considering how much easier it would be to deal with all the types and validations and stuff.

As it stands, the Readme doesn't even mention the possibility of using this as a Library, and from what little code I skimmed through it seems there were no plans to have this work as anything other than a CLI program, but what I've seen also indicates that, although there a few prints here and there, there are actually not that many places in the code that depend on user interaction, and this suggests that it may not be that hard to isolate such interactions from the code that actually deals with the provides, making it more straightforward to use this as a library in other Rust projects.

Though, obviously, there's a need to decide on how useful such changes would be and whether it'd be worth doing such changes, but that's not for me to decide so I just came to point it out.

The binaries can be automatically built and published via a GitHub action whenever a new git tag is pushed to this repository. I also think it might be convenient to have a install.sh script that downloads the latest binary and places it in /usr/local/bin.

These files could be used as a reference if needed:

• https://github.com/ducaale/xh/blob/master/.github/workflows/release.yaml
• https://github.com/ducaale/xh/blob/master/install.sh

It would be great to download magnets for download at a later time, particularly for those using unsupported clients - like transmission etc. I will try to take a crack at this...

Hi! I think it would be nice to support proxies, since torrent trackers are blocked in some countries. I haven't look at your code, but Cargo.toml indicates that you use reqwest, which does support proxies. I would start from socks, since it allows one to use tor. Do you need help with that?

would be good to have an option like --no-interactive to have the results only be the name, then a tab character, then the magnet link, e.g.

> magnetfinder -aq 'big buck bunny'
big-buck-bunny-NTSC.iso	magnet:?xt=urn:btih:FC84B941DC640BE59C90D7AB58819D50EDCFF906&dn=big-buck-bunny-NTSC.iso
Big Buck Bunny 480p (x264, he-aac)	magnet:?xt=urn:btih:05D51D7153228E08D94F850E5D2CE0A9E764752E&dn=Big+Buck+Bunny+480p+%28x264%2C+he-aac%29

would also be good for a paramater to specify how many results/rows should be returned