Our great sponsors
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
transgui
🧲 A feature rich cross platform Transmission BitTorrent client. Faster and has more functionality than the built-in web GUI.
-
-
-
flood
A modern web UI for various torrent clients with a Node.js backend and React frontend. (by jesec)
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
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...
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...
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.
Qbittorent in particular has had several http exploits in the past. The most recent was a few months ago: https://github.com/qbittorrent/qBittorrent/issues/18618
Putting nginx in front with http basic auth would prevent all of them.
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
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
Related posts
- Transmission 4.0.0 beta 1 is out
- What's the best, fastest, and free way for someone to share their 1.6 TB audiobook collection with me?
- Services for large P2P file transfers in browser?
- how do i make my own Torrent File and sending it to my friend and not stalles
- [Home Lab] Transmission vs qbittorent vs déluge pour le serveur torrent distant?