Revisiones de Torrent Control
Torrent Control por Aiken
129 revisiones
- Se valoró con 5 de 5por Usuario de Firefox 15104605, el hace 4 años
- Se valoró con 5 de 5por stampedes, el hace 4 años
- Se valoró con 4 de 5por Rymrgand, el hace 4 años
- Se valoró con 5 de 5por mbesar, el hace 5 años
- Se valoró con 5 de 5por SeriouslySerial, el hace 5 añosWorks perfectly for what I need it to do. Thank you very much for creating this.
- Se valoró con 4 de 5por Usuario de Firefox 13466126, el hace 5 años
- Se valoró con 5 de 5por Davide, el hace 5 años
- Se valoró con 5 de 5por mmmel4real, el hace 5 añosVery nice. Works much better than the alternative extension. Suggestion: A generic client option that simply adds a torrent file to a folder where our client can be set to detect it.
- Se valoró con 4 de 5por shimi269, el hace 5 añosIt's a really good torrent adder, but the notifcation pop-ups are annoying. Their are appearing broken, showing the HTML code, instead of actual text. Having the option to make the pop-ups turn off, or be fixed would make this into the best remote torrent adder on Firefox.
Respuesta del desarrollador
publicado el hace 5 añosAddon shows plain html for unkown responses so that you can fix the issue causing it. These mostly appear on seedbox hosts who use modified bittorrent clients. Notification setting is on the todo list - Se valoró con 5 de 5por Imrus, el hace 5 años
- Se valoró con 5 de 5por Usuario de Firefox 15126972, el hace 5 añosworks great with deluge on unraid
- Se valoró con 5 de 5por mrp_x, el hace 5 años
- Se valoró con 4 de 5por Needle, el hace 5 años
- Se valoró con 5 de 5por Barafu Albino Cheetah, el hace 5 añosWorks very nice! Tried it With ruTorrent and Deluge. Thank you a lot!
A suggestion: Could you please add an option to disable notification about torrent successfully added? Torrent UI sends the same notification itself, and I get double notification. I'd prefer UI's notification only, because it is more meaningful.
Another suggestion: you should write a Youtube downloading addon with opensource backend. *All* existing options are both closedsource and scummy. You will be the king of extensions with those two. Just make an in-browser UI for youtube-dl and ffmpeg. - Se valoró con 3 de 5por Usuario de Firefox 15108566, el hace 5 añosI think the client app drop down list should have Flud rather than Flood
Respuesta del desarrollador
publicado el hace 5 añosUnfortunately Flud doesn't have web interface to communicate with. - Se valoró con 2 de 5por Zachary Hill, el hace 5 añosLooks good, but doesn't work for me, always get 404. I know the path and auth are right, clicking the icon even brings me to the right page, but adding magnet links doesn't work. (I think because it's under a /path, due to being behind a reverse proxy) I've used other things that work with the API, so the reverse proxy is okay, I think your extension just doesn't like example.com/rtorrent as my path. Any way I can get a hotfix for this? Another potential problem is that your extension may be doing DNS lookup for the path with its own DNS server. (As my path resolves differently from my internal DNS server than it does for external servers)
Respuesta del desarrollador
publicado el hace 5 añosClients installed in subpaths are supported and should work fine. Can you open an issue on Github with specific client/webui etc. versions, so I can take a closer look at this? - Se valoró con 5 de 5por Usuario de Firefox 15043727, el hace 5 añosbeautiful plugin, works perfectly as advertised.
- Se valoró con 4 de 5por Usuario de Firefox 14890484, el hace 5 añosAfter extension's crash doesn't work. Unknown response, 403: Forbidden :-(
Suddenly it works again. What was it?... - Se valoró con 1 de 5por Usuario de Firefox 14781029, el hace 5 añosNo disponibilidad para MacOS incomprensible.
- Se valoró con 3 de 5por Usuario de Firefox 13657772, el hace 5 añosNot working with Transmission - Error - Unknown Response (405: Method not allowed)
Respuesta del desarrollador
publicado el hace 5 añosThis error most often means that your server path is wrong. On transmission you should point the path to transmission root (most likely http://127.0.0.1:9091/) and not http://127.0.0.1:9091/transmission/web/ - Se valoró con 5 de 5por Usuario de Firefox 14757090, el hace 5 añosThis is fantastic. Thanks for writing this and having the code on github. I dug around the code as the permissions concerned me, but I didn't see it phoning anywhere except to your assigned torrent UI. I haven't decompiled the extension yet but assuming that goes well and matches the github source I see no concerns over the permissions and they make sense since you don't have a site white list (which I'd recommend as a feature request to limit permissions in the future).
Respuesta del desarrollador
publicado el hace 5 añosUsing minimum amount of permissions is one of my design goals. Hopefully we can get rid of "use data on all sites"-permission when content handler supports comes available.