Pohódnoćenja za Torrent Control
Torrent Control wot Aiken
145 pohódnoćenjow
- Z 4 z 5 pohódnoćenywot Wužiwar Firefox 13466126, prije 6 godina
- Z 5 z 5 pohódnoćenywot Davide, prije 6 godina
- Z 5 z 5 pohódnoćenywot mmmel4real, prije 6 godinaVery 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.
- Z 4 z 5 pohódnoćenywot shimi269, prije 6 godinaIt'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.
Wotmołwa wuwiwarja
je so prije 6 godina napisałAddon 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 - Z 5 z 5 pohódnoćenywot Imrus, prije 6 godina
- Z 5 z 5 pohódnoćenywot mrp_x, prije 6 godina
- Z 4 z 5 pohódnoćenywot Needle, prije 6 godina
- Z 5 z 5 pohódnoćenywot Barafu Albino Cheetah, prije 6 godinaWorks 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. - Z 3 z 5 pohódnoćenywot Wužiwar Firefox 15108566, prije 7 godinaI think the client app drop down list should have Flud rather than Flood
Wotmołwa wuwiwarja
je so prije 7 godina napisałUnfortunately Flud doesn't have web interface to communicate with. - Z 2 z 5 pohódnoćenywot Zachary Hill, prije 7 godinaLooks 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)
Wotmołwa wuwiwarja
je so prije 7 godina napisałClients 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? - Z 5 z 5 pohódnoćenywot Wužiwar Firefox 15043727, prije 7 godinabeautiful plugin, works perfectly as advertised.
- Z 4 z 5 pohódnoćenywot Wužiwar Firefox 14890484, prije 7 godinaAfter extension's crash doesn't work. Unknown response, 403: Forbidden :-(
Suddenly it works again. What was it?... - Z 1 z 5 pohódnoćenywot Wužiwar Firefox 14781029, prije 7 godinaNo disponibilidad para MacOS incomprensible.
- Z 3 z 5 pohódnoćenywot Wužiwar Firefox 13657772, prije 7 godinaNot working with Transmission - Error - Unknown Response (405: Method not allowed)
Wotmołwa wuwiwarja
je so prije 7 godina napisałThis 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/ - Z 5 z 5 pohódnoćenywot Wužiwar Firefox 14757090, prije 7 godinaThis 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).
Wotmołwa wuwiwarja
je so prije 7 godina napisałUsing 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. - Z 5 z 5 pohódnoćenywot Wužiwar Firefox 14754748, prije 7 godina
- Z 4 z 5 pohódnoćenywot Wužiwar Firefox 14732770, prije 7 godinaThanks for this; it works, but is somewhat limited. I wish I could select the download path and labels out of a dropdown when clicking a torrent. If that's too complicated, maybe we could at least set a default download path to be used when left-clicking torrents - right now it seems to send it off without a path supplied unless you navigate the context menu options.
Wotmołwa wuwiwarja
je so prije 7 godina napisałI have planned including "Add with advanced options"-window which would allow selecting download directory, labels and possibly bulk adding torrents. Hopefully I have time to add it in some point, - Z 4 z 5 pohódnoćenywot megaslx, prije 7 godina
- Z 4 z 5 pohódnoćenywot Wužiwar Firefox 14625698, prije 7 godina
- Z 4 z 5 pohódnoćenywot Wužiwar Firefox 14623833, prije 7 godina
- Z 5 z 5 pohódnoćenywot Ģααŗα™, prije 7 godina
- Z 5 z 5 pohódnoćenywot Wužiwar Firefox 14597458, prije 7 godinaThis extension allows me to send a magnet link to my VPN'd VM Seedbox running Qbittorrent and pick what directory I want the file to download to. Apps like this can improve a torrent program so much.
- Z 1 z 5 pohódnoćenywot Wužiwar Firefox 14572408, prije 7 godinaDoesn't work.
edit: Adding torrent fails every time with an extremely unhelpful "Network error". No further details or instructions given in the UI or in the documentation.Wotmołwa wuwiwarja
je so prije 7 godina napisałCan't really do anything without details.
Edit: Firefox doesn't expose more detailed error messages about network communication. Authentication etc. do have their own error messages. This is most likely related to wrong hostname or port (or about anything from firewall to cable not plugged).