[squarefoot]

Support in the browser would require the browser to stay on the whole time, along with the computer. Bittorrent clients are better run on small less power hungry boards (RPi, etc.) or on hardware that is meant to be running 24/7 anyway. For example, I run the Transmission daemon on my XigmaNAS home file server. The NAS is headless, but I can control the daemon through its remote GUI, so as soon as I click on a torrent or magnet link on the browser, it calls the local Transmission GUI which sends the info to the client on the NAS which starts the download freeing the browser and the PC of any further work.

https://xigmanas.com/xnaswp/

https://github.com/transmission-remote-gui/transgui

[ycombinete]

I don’t know about others, but my browser is open about 100% of the time

[Lhiw]

Yea this was a super weird complaint. My browser is open for far more time than my torrent app.

[WithinReason]

It would absolutely not require that, it only requires that someone's browser is open when you're trying to download, which is likely since most people have their browsers open a lot.

[sleavey]

It doesn't require the browser to be always on, unless you want to download something (which is the same as a normal download). Do you mean it's better for the health of the swarm for a particular file? Otherwise I'm not sure I get your point.

[squarefoot]

> Do you mean it's better for the health of the swarm for a particular file?

That is one of the main points. Some files are shared by thousands users and can be downloaded in seconds, but others are much harder to find, so that I like to keep the client on to help other people getting it quickly. I usually am annoyed when a file with a single seed reaches like 97% then it dies until the following day because the seeder had to turn off the PC, so I try to avoid this, especially since it costs me nothing as broadband is flat and the client runs on a machine that is always on.

[bmn__]

https://press.opera.com/2006/02/06/opera-integrates-bittorre...