instant.io VS Transmission

- https://instant.io

these, but they won't hide your IP so you probably will need to use them with a VPN - https://instant.io/ - https://btorrent.xyz/ - https://ferrolho.github.io/magnet-player/

The page mentions the possibility of file sharing/torrents using WebRTC which does exist if anyone is interested: https://webtorrent.io/ and https://instant.io/

The projects are open source: https://github.com/webtorrent/webtorrent

I wish there was a command line program like this, but one that would make a torrent of that file [1] and return a magnet link for the torrent.

The next weak point is the centralization around the tracker. You can solve this by sharing all the tracker information on Nostr [2], maybe?

1. https://instant.io

Option #2 https://instant.io/ (unlimited size - uses WebTorrent)

If I had to mention, it would be Instant.io for your reference.

Not sure who this is for? It looks like something made for casual users, but I'm not sure that they need a web UI for remote control or CLI.

More advanced users are very unlikely to use something with such UI. I can't imagine that it will be fun to use while having 10 torrents, let alone 250+.

Even Fragments[1], the GNOME Circle app for BitTorrent that targets casuals can fit more downloads in a single view.

And what's the point of the search bar? All it does is open a new tab and search "torrent " in either Google or DDG. I can do it myself. It's neither helping newbies nor advanced users.

Also the 1.7M package-lock.json[2] scares me, but so do most JavaScript projects. Do we really need that many JS libraries for a UI for a BitTorrent client?

In comparison, Transmission's web UI has a package.json that uses 354K[3].

1: https://apps.gnome.org/en-GB/app/de.haeckerfelix.Fragments/

2: https://github.com/G-Ray/pikatorrent/blob/main/package-lock....

3: https://github.com/transmission/transmission/blob/main/web/p...

Why bake libtransmission into the app instead of just using the transmission daemon's RPC?

What you've done actually makes it harder to use, because in order to configure any of transmission's settings (ports, connection/torrent connection limits, bandwith limits, etc) the user needs to dig around to find the transmission config folder and then manually edit JSON with a text editor - because your client doesn't expose any of transmissions numerous settings [1] to the user except for choosing the download folder.

I'm not sure why anyone would want to use this instead of Flood [2] or even old Transmission Web Control [3]

1: https://github.com/transmission/transmission/blob/main/docs/...

1: https://github.com/jesec/flood

2: https://github.com/ronggang/transmission-web-control

Its intresting you mention that, before reading your reply I went and created a post in the Q n A section, asking for help about this very thing and I linked to the same GitHub issue you linked to here. I have yet to get a reply lol.here

A un grand wiki

Transmission

https://github.com/transmission/transmission/blob/main/docs/Scripts.md https://github.com/transmission/transmission/blob/main/docs/Editing-Configuration-Files.md

Note that I'm running merferfs 2.35.1 and Transmission daemon 4.0.2 (2a57b17031) (the latter was one release behind at the time of the error).

(The BitTorrent client is something I don't use. I do use a ~very old predecessor, uTorrent {v1.6.1}; I think BitTorrent is the current client born of it... long since bought-out. You should really be using qBitTorrent or even Transmission...