webtorrent VS transgui

It's because of the kind of content that is shared. BitTorrent serves a lot of content you are not allowed to redistribute, so having an open gateway immediately puts you at risk of aiding the distribution of content. But it does work, someone even made something native to browsers so browsers themselves can share content: https://webtorrent.io/. There are even fuse "gateways" to make it native to your computer and pretend the files exist locally: https://github.com/search?q=bittorrent+fuse&type=repositorie...

IPFS doesn't seem to be used for that kind of content much, it seems to be targeted more towards web-native content (html pages, images, that kind of stuff). It's probably safer for Cloudflare to run this.

title. I have some experience with c++ but not much with torrent libraries. (webtorrent, stremio)

You can stream torrents

If it fits your model, WebTorrent[0] can offload a lot of bandwidth to peers.

[0] https://github.com/webtorrent/webtorrent

Then https://github.com/webtorrent/webtorrent could be used to actually download the videos in browser, the idea being here though, that you would at least seed out as much as you got. Enabling other's to access videos without requiring creators have the infrastructure to push a video to 1000s or more clients at once.

I assume you've seen https://webtorrent.io/ ?

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.