Om duisende beskikbare byvoegings te probeer, laai Mozilla Firefox af, 'n gratis en vinnige manier om deur die Web te blaai!Close
Welkom by Firefox Byvoegings.
Kies uit duisende ekstra funksies en style om Firefox nommerpas te maak.Close
Aangaande dié byvoeging
Supported Torrent programs and minimum versions supported
µTorrent, version 3.* for full support, version 2 also works
BitTorrent, v7.* (v6?)
qBittorrent v2.*, v3.1 (v3.2 not supported yet)
Deluge, partial support for 1.2.*, full support for 1.3.*, 1.3.4 needed for magnet links
KTorrent, 4.2 (4.0?)
Transmission, 1.3 or greater
Vuze, HTML WebUI 0.7.6 or azSMRC 1.0.0 or Web Remote 0.1.3.
Upgraded to Firefox 42 and can't connect? You may need to check your cookie exceptions. A simple hostname is no longer sufficient for secure non-standard ports usually used for webuis. So for example, instead of just localhost you will need to add an exception for localhost:9091.
- toolbar icon or label showing current upload and download stats
- panel layout for horizontal or vertical toolbars
- summary torrent list in a popup panel (hover on menuitem, hover on full panel, or ctrl+hover on icon)
- one-click access to the full WebUI interface opening in place or in a new tab or window
- support for as many different servers as you like
- control from the toolbar context menu or tools submenu
- commands to pause or unpause all torrents
- one click submission of torrents from the browser, either as magnet links or files
- "native" balloon notifications or Firefox alert boxes
First make sure your program is configured to support a webui in the browser. If it doesn't then Torrent Status is unlikely to work.
1. Open the toolbar customise dialog and drag one of the Torrent Status icons to wherever you want it.
2. You might connect automatically, but if not open the options dialog and go to the server tab.
3. Select the type of torrent program you have from the list. It may connect automatically or ask you to login.
4. If you have changed the webui port for your program, enter it. If you have configured SSL/HTTPS, click the box.
5. Torrent Status should find most local and many LAN servers automatically, but if not then you'll have to enter the IP address or domain name manually.
6. Login if necessary.
There is a statusbar panel icon that can be selected to appear. This is not recommended since the statusbar will be removed at some stage, but if you still use it then you can check this box.
In the options dialog, on the Appearance tab, you can filter the torrents that will appear in the quick list. All are selected by default, but if the list is too long then you can exclude certain categories. You can also change the small summary tooltip format and disable the feature that changes it to the torrent list when you hold down the control key.
On the Polling tab, you can change the polling intervals and network timeout values, and select whether to poll faster when you hover the mouse over the Torrent Status toolbar item.
On the Add Torrents and WebUI tabs you can select whether to one-click add magnet links and torrent files to the connected server, the types of notifications to receive, and where to open the webui from Torrent Status.
On the Servers tab, you can configure the details for your server connection. The name and icons do not affect the connection but you can change them so suit. The default settings should be filled in automatically, but if you change your configuration or have a remote server then you'll need to fill in the correct details. Some programs require the webui to be activated or a plugin to be installed before they can be used.
- uTorrent and BitTorrent should automatically have a webui or prompt you to download one the first time you try to use it.
- qBittorrent has a webui built in, but you need to activate it from the options in the program.
- Deluge can be run as a standalone program or a daemon. As a classic program, the webui needs to be activated from the options and usually must be downloaded as a separate package first. The daemon requires a separate webui package to be installed and connected. You are responsible for connecting to the correct daemon before Torrent Status can run,
- KTorrent requires a webui plugin to be activated, but it is usually included with the standard install.
- Transmission requires the build in web interface to be enabled from the options. Or you can just run the transmission-daemon without any other client UI.
- Vuze (formerly Azureus) requires a plugin to be installed and activated before Torrent Status can be used. Three plugins are supported: HTML WebUI, azSMRC Remote Control, or Vuze Web Remote.
It is recommended to use authentication and change the default login details if your server is publicly accessible, and obviously it must be publicly accessible to work. Unless you are confident that your router or firewall blocks the webui port or external webui access is otherwise restricted to just your computer, enable authentication and enter a strong password. Most torrent programs include default usernames and passwords to help you get connected, but you will usually want to change them. If your torrent server does not require authentication then you can leave the username and password settings in Torrent Status alone. Unless the "Send empty password ..." box is checked, you will be prompted for a password as soon as a server that requires authentication is connected. If the box is checked then you will never be prompted for a login and a blank password will be sent with the configured username whenever a server requests authentication. You can have the password saved in the Firefox vault, or you can enter it each time you start Firefox.
You can enter configurations for more than one type of torrent program, although torrents will only be shown from one at a time. You can select the one to be polled from the Torrent Status context menu or the options dialog. Click the dropdown on the Servers tab to add a new server entry, or to delete or reorder existing ones.
It may be frustrating when you are not instantly connected after installation. The first step is to check your server configuration in the options dialog. The default values will work for some people, but the server address will often not match your situation. When making changes, it may take up to a few seconds for the connection to reset so don't panic. Use the WebUI to check what you think are the connection details, for example http://127.0.0.1:8080:/gui/. Automatic server discovery is now quite good for localhost and other likely local network addresses, but it requires the correct port.
When you're convinced you have the right connection details, make sure that cookies are allowed for the server address. Cookies are usually used as part of the authentication process. If you generally have cookies blocked, add an exception for the server address. Again, if the WebUI works then the addon should work. The Cookie Controller addon makes it easier to work with cookie permissions and exceptions. You don't have to allow third party cookies and you can restrict cookies to expire at the end of the session.
Watch out for servers that lock you out for entering the wrong password too many times such as qBittorrent. You'll need to restart the program and try again with the correct details.
If you are pestered with password prompts, make sure that your options settings match the webUI configuration and you allow Firefdox to remember your password. If you select for Firefox to remember the password then you should never see an authorisation prompt from the addon again, although the WebUI may produce one if you restart Firefox.
Although this extension is primarily for tracking the status of torrent downloads, it also supports adding torrents through the webui API. Magnet links are taken by a "magnet:" protocol handler and submitted as a URL. Most webUI APIs return OK whether or not a torrent was successfully added. A valid magnet link should always be added, although it may already exist. A valid torrent file will generally be added, but again it may already exist.
Torrent files are identified using content type "application/x-bittorrent". Some servers use "application/octet-stream" or very rarely something else, and these will be detected only if the filename ends ".torrent". In practice this detects every torrent file link I've ever seen. If you spot something that doesn't work then let me know. The file is passed to a content handler, read using a stream listener, and then uploaded. This may take several seconds, but a successful upload is a fairly reliable indication that the torrent was added. In some cases an invalid file or duplicate torrent may not get added, but there is no confirmation of this and you'll just have to look in the torrent list.
The addon uses token authorisation with µTorrent and Bittorrent to prevent a known exploit of the basic authentication API. qBittorrent uses digest authorisation that is not vulnerable to this exploit, so no need for tokens. Username and password authorisation is fully supported, with passwords stored securely in the Mozilla logjn manager. Authentication details are only sent out when a 401 response is received on the configured address with the expected realm for that server type.
Please raise bugs or enhancement requests on the support page. It is impossible to fix bugs reported in a review that cannot be reproduced. There is also a discussion thread about this extension.
The Development Channel lets you test an experimental new version of this add-on before it's released to the general public. Once you install the development version, you will continue to get updates from this channel. To stop receiving development updates, reinstall the default version from the link above.
Caution: Development versions of this add-on have not been reviewed by Mozilla.
- Weergawe 2.0b2: