I have had to migrate from Transmission to BiglyBT because the former has become increasingly unreliable and/or unstable.
Although I’m very happy with Bigly, I’m surprised by how (relatively) cumbersome it is.
Instead of (say) instantly loading the torrent link or file (like every other torrent app) an ‘operation in progress’ box appears and takes a while to load or connect to the torrent. It’s not just the distended operation though - you’re required to stay within the app until it connects.
If you try to (say) browse online or use another app like Word, the ‘operation’ actively prevents you from doing this or will automatically return you to Bigly until the initial operation is complete.
And then, of course, shutting down the app seems to be a whole production too. Instead of just immediately quitting like every other app, you’ll get another ‘operation in progress’ box appear as it shuts down and quitting the app can take a while too (up to 20 seconds).
Is there anyway of turning off this box hijacking or letting these distinct operations occur behind the scenes instead?
thanks
Isn’t biglyBT an i2p and Java based solution? It’s going to be much heavier and slower. That’s just the nature of the beast.
I won’t use BiglyBT, though that’s mostly out of my pettiness toward Oracle/Java technology. QBitTorrent is fine.
And if you are seeing anyway, you should probably being doing from a box you control that the cloud can’t be used to attack so soon up a cheap Linux or BSD box somewhere on your network and use the webUI on your Mac.