transmission-web-control
transgui
transmission-web-control | transgui | |
---|---|---|
6 | 25 | |
4,503 | 3,150 | |
- | 0.7% | |
3.5 | 5.2 | |
26 days ago | 2 months ago | |
CSS | Pascal | |
MIT License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
transmission-web-control
-
Show HN: PikaTorrent, a modern, multi-platform, open source BitTorrent app
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
-
I ditched those two and never looked back since
The remote UI was the one downside of Transmission, until this came out: https://github.com/ronggang/transmission-web-control
-
Transmission with Web Control
I have been able to install this: https://github.com/ronggang/transmission-web-control/wiki, in the transmission image.
-
I went a bit overboard customising Heimdall
Transmission also has alternative Web UIs that you can use: Combustion, Transmission Web Control, kettu and Flood for Transmission. The LinuxServer.io Transmission container has support for all of these.
-
Best Torrent Client?
UI is not too bad - docker container comes with bundled Transmission Web Control UI or standalone Transmission Remote GUI can be used on client...
-
Consider replacing BitTorrent and uTorrent with Transmission: a FOSS alternative
+1 for Transmission Remote GUI. Also, in a pinch, this web UI is quite a bit better than the default one: https://github.com/ronggang/transmission-web-control/wiki.
transgui
-
Show HN: PikaTorrent, a modern, multi-platform, open source BitTorrent app
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.
-
[Home Lab] Transmission vs qbittorent vs déluge pour le serveur torrent distant?
Client éloigné prometteur tiers
- [Torrents] qBittorrent vs Transmission. Comment parvenez-vous à trier les torrents?
-
[Homelab] Transmission vs Qbittorent vs Deluge pour serveur torrent distant?
Client distant tiers prometteur
-
Transmission v4.0
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
-
Vpns for plex
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
-
Transmission 4.0.0 beta 1 is out
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
-
Using private trackers on home server?
Transmission Remote GUI
- Is there more settings for haugene Transmission?
-
groffstudio: An IDE for groff
This explains why the only other Lazarus project I know (transgui) is very similar, a GUI to another program.
What are some alternatives?
combustion - Simple, elegant testing for Rails Engines
transmission-remote-gtk - transmission-remote-gtk is a GTK client for remote management of the Transmission BitTorrent client, using its HTTP RPC protocol.
kettu - Rewrite of the Transmission Web Client with jQuery, Sammy and Mustache
docker-transmission-openvpn - Docker container running Transmission torrent client with WebUI over an OpenVPN tunnel
flood-for-transmission - A Flood (https://github.com/Flood-UI/flood) clone for Transmission
rtorrent - rTorrent BitTorrent client
combustion - Combustion is a sleek, modern web interface for Transmission
webtorrent - ⚡️ Streaming torrent client for the web
Organizr - HTPC/Homelab Services Organizer - Written in PHP
spksrc - Cross compilation framework to create native packages for the Synology's NAS
bt2qbt - bt2qbt is cli tool for export from uTorrent\Bittorrent into qBittorrent
dottorrent-gui - An advanced GUI torrent file creator with batch functionality, powered by PyQt and dottorrent