Any of them also supports WebTorrent?

I love and use qbittorrent exclusively but it gets bogged down when it has lots of torrents going. A-tier at best.

I am still using the last (ancient) version of Azureus (Vuze) because it has great plugins. I have the plugin to allow it to use the Mainline DHT, and I use the i2p plugin too (because the default i2p torrent UI is bad). Azureus is (was) the only client that can download/seed a torrent on clearnet and i2p at the same time.

Having said that, I didn't know that BiglyBT has i2p support, so I need to check that out.

Good list. Honestly, if it doesn't have network interface binding it's not a even an option for me. It's so important to keep your IP from leaking, it should be a priority feature.

I switched an old delapidated version of QBit a few years ago for Deluge, they're both cool I guess.

Why is Tixati banned?

Is there a docker container for BiglyBT that handles java and has a webUI, similar to qBittorrent? And can it integrate with the *arrs in the same way?

I'm still liking DS Get. I choose torrent files on my phone then hand off the download to the NAS.

I want to use qbittorrent, but my Mac won't let me install it - says it's too old for the operating system and/or that it can't be verified.

I've just installed bigly bt, and I have three questions: 1) is it possible to set the seeding ratio 2) do we really need to confirm the deletion of every torrent via the pop up? (I have RSI, and the less popups or clicking the better) and 3) why does searching for a torrent via the internal search engine result in a captula.?

It's completely overkill for pretty much everyone but I have been thinking about building a kubernetes native client for months now.

Like the torrent should be treated as a normal resource with a Torrent CRD. It should be scheduled onto whichever node has available capacity and rescheduled onto a different node if it goes down. If allowed by the tracker, multiple instances could be run. You could set resource limits programmatically, easily configure block storage, build dashboards, export logs/metrics.. It would be open ended enough that you could have interfaces built as browser extensions, web ui, mobile app, tui, cli and be unopinionated so much that the method for torrent ingestions could be left up to the used. HTTP request, watch directory, rss client, download manager.. You could even do stuff like throw magnet links into a queue.. etc, etc..

I keep thinking it would be a great project but I just do not have the spare time to dedicate to it.. I imagine it could be used for large scale deployments for something like the Internet archive or whatever.

On android I'm currently using Libretorrent, how does biglybt's android app compare to it ?