transgui VS libtorrent

For example, down that page there's a Transmission remote GUI screenshot (I use it as Transmission here is a daemon on my headless XigmaNAS server).

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

What would be wrong with it or anything similar? Every information is just there, no need to swipe left and right to read information that has been either hidden elsewhere or, worse, taken away.

Client éloigné prometteur tiers

Client distant tiers prometteur

Actually, not such a bad question. There's at least Synapse[1]. It even has a third-part broker to accept transmission GUIs by Drew Dewalt[2]. Why didn't they just reuse Transmission protocol from the get-go, to leverage the great Transmission-Remote-GUI[3] for example, is beyond me.

Unfortunately, there's just not enough interest in the project and no adoptance.

Transmission, at least previously, never have been too resource-friendly, so a lean and mean Rust alternative would be great.

1. https://github.com/Luminarys/synapse

2. https://sr.ht/~sircmpwn/broca/

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

For something a bit easier I'd look into Transmission or Deluge. The big difference is qbittorrent ran headless only has a web interface, whereas deluge and transmission both have remote dekstop clients as well mobile-friendly web interfaces and apps available

If someone asks me to install a Torrent client on a single machine, my favorite would be QBittorrent, however at home I use XigmaNAS' Transmission client extensively, and operate it from other machines in the LAN using the Transgui interface (also available on Windows and MacOS). This allows me to turn off everything but the NAS, which with all RAID disks spun down and a TDP of 15 Watts makes for some good energy savings.

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

Transmission Remote GUI

This explains why the only other Lazarus project I know (transgui) is very similar, a GUI to another program.

I had a longer answer, but qBittorrent is great and has a great webui/server model if you're running a separate linux box to run it in. If you're on windows, grab 4.3.9 or 4.6.2 with libtorrent 1.x. RSS stuff is nice too. Libtorrent 2.x has issues on Windows currently (read these threads if you want to know more - https://github.com/arvidn/libtorrent/pull/7013 - https://github.com/arvidn/libtorrent/issues/6667#issuecomment-1804035311 ). Please don't bug Arvid about it though. Libtorrent 2.x gets us Bittorrent v2, which is a good thing.

Latest libtorrent v1.2 branch changelog: https://github.com/arvidn/libtorrent/blob/RC_2_0/ChangeLog

You can support this feature by writing a comment in https://github.com/arvidn/libtorrent/issues/7252

Where users could finally download files that were present in other swarms. This would decentralize network more, swarms with valuable files wouldn't die fast, even when updating a torrent, where info hash differs, say tv series, adding new episode, all the previous seeds of swarm could contribute bandwidth and resistance to new swarms, there were nice proposals at libtorrent project (library which many clients we know use), as f.e. not announcing that a peer has files to not overwhelm network, but announcing that he wants them.

How much of it do you want to do yourself vs how much do you want to use pre-made libraries for? Many popular clients rely on libtorrent which is a C++ torrent library: https://github.com/arvidn/libtorrent

FWIW, it seems like there'll be an update to libtorrent very soon that'll address the memory issue.

Here is a link to an issue I found on the libtorrent repo discussing the issue.

Many!

https://webtorrent.io/faq

Notable ones include Libtorrent[1], Peertube[2], and their own Webtorrent Desktop[3].

1. https://github.com/arvidn/libtorrent/issues/223

2. https://peertube-viewer.com/posts/2021-02-20-peertube-viewer...

3. https://webtorrent.io/desktop/