picotorrent VS libtorrent

While the torrent client included in the owntinfoil zip is open source, the two .exe's included are not, and he's actually violating the open source license for https://github.com/picotorrent/picotorrent

You can look the code of PicoTorrent, is a clean and small client (based on libtorrent too) : https://github.com/picotorrent/picotorrent

Love Transmission but went to picotorrent a few years ago, even smaller footprint https://github.com/picotorrent/picotorrent

I wish some of the other BT clients took off besides the big 3 (Qbt, Deluge, Transmission and I guess rtorrent+rutorrent as well). There are some other simple BT clients out there that mimic early uTorrent GUI, one of the most notable was Hadouken, which was headless. It had a web UI that's reminiscent of uTorrent 2.0.4. https://github.com/hadouken/hadouken Sadly the project seems dead, as the last official release was in 2015. There's another minimal torrent client named Picotorrent available for Windows https://github.com/picotorrent/picotorrent, but I am not sure how well this works on heavy libraries, and I doubt many private trackers allow it because it's so niche. Another client I used to use back in the day was Halite, but that also died in 2015.

Not really true - v0.20 of PicoTorrent [1] was released the same day as libtorrent released support for v2 torrents. I think this predates BiglyBT 2.5 with v2 [2] support with about two weeks.

[1] https://github.com/picotorrent/picotorrent/releases/tag/v0.2...

Picotorrent which I have never personally used but which I have heard good things about: https://github.com/picotorrent/picotorrent

A new windows client built on C++, picotorrent

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/