Poco intuitivo e non apre i torrent salvati sul PC. Disinstallato subito!

Worked for quite some time but I think when Firefox updated and patched, this broke.

It stopped me downloading the .torrent file, so I stopped using this add-on, then I could start downloading the .torrent file again

Works with qBitorrent.

does what it's meant to be very well

Works as expected!

Good job

Works perfectly for what I need it to do. Thank you very much for creating this.

Very nice. Works much better than the alternative extension. Suggestion: A generic client option that simply adds a torrent file to a folder where our client can be set to detect it.

It's a really good torrent adder, but the notifcation pop-ups are annoying. Their are appearing broken, showing the HTML code, instead of actual text. Having the option to make the pop-ups turn off, or be fixed would make this into the best remote torrent adder on Firefox.

works great with deluge on unraid

Works very nice! Tried it With ruTorrent and Deluge. Thank you a lot!
A suggestion: Could you please add an option to disable notification about torrent successfully added? Torrent UI sends the same notification itself, and I get double notification. I'd prefer UI's notification only, because it is more meaningful.
Another suggestion: you should write a Youtube downloading addon with opensource backend. *All* existing options are both closedsource and scummy. You will be the king of extensions with those two. Just make an in-browser UI for youtube-dl and ffmpeg.

I think the client app drop down list should have Flud rather than Flood

Looks good, but doesn't work for me, always get 404. I know the path and auth are right, clicking the icon even brings me to the right page, but adding magnet links doesn't work. (I think because it's under a /path, due to being behind a reverse proxy) I've used other things that work with the API, so the reverse proxy is okay, I think your extension just doesn't like example.com/rtorrent as my path. Any way I can get a hotfix for this? Another potential problem is that your extension may be doing DNS lookup for the path with its own DNS server. (As my path resolves differently from my internal DNS server than it does for external servers)