In Vuze/Azureus, it's not necessary to change the magnet link, so I suppose it would be the same for rtorrent.
However, I have also not been able to use the magnet links with rtorrent (tried repository package).
In Vuze/Azureus, it's not necessary to change the magnet link, so I suppose it would be the same for rtorrent.
However, I have also not been able to use the magnet links with rtorrent (tried repository package).
It works with uTorrent 1.8.5 through wine...
Does anyone know, how to make magnet links work with KDE+Firefox+Deluge? I've tried adding those two settings in about:config with Deluges path (/usr/bin/deluge), but it doesn't work.
the only client I care about is rtorrent
http://libtorrent.rakshasa.no/ticket/955
"I took the red pill, but I installed the blue Linux"
Archlinux user, using it right now.
Mine works with karmic Kubuntu AMD64
The about:config above has an error in the syntax
network.protocol-handler.app.magnet /usr/bin/deluge
network.protocol-handler.external.magnet true
plus run these gconf commands amending to deluge rather than azureus
http://ubuntuforums.org/showthread.php?t=229924
The first time it runs it will ask if you want to make deluge the default magnet handler, thereafter it just fires up deluge and starts. Magnets look a bit different and take a bit longer to start than torrents so don't panic if it looks different for the first 30 seconds.
ps
It is not easy to fix stuffed about:config entries. You will need to open ~/.mozilla/firefox/xxxxxxxx/prefs.js with kate and fix the entry that is wrong, where xxxxxxxx is a bunch of letters and numbers that is different for each install.
Hi! I think I have a similar problem to anders_c.
I can't open the magnet links on TPB, but on mininova isn't it a problem. I run ubuntu karmic, firefox 3.5.5 and vuze v4. The magnet link URI looks diffrent. Example with a US Now torrent (legal):
Do anyone know anything about this? Anders, does the links work on mininova for you?Code:TPB: magnet:?xt=urn:btih:24ec1f97b8288b15943096278dcf11c4487416e0&dn=US_NOW-720.mp4&tr=http://tracker.openbittorrent.com/announce Mininova: magnet:?xt=urn:btih:ETWB7F5YFCFRLFBQSYTY3TYRYREHIFXA
EDIT:
I saw this help after i posted.
lunatic1234 wrote:
However, Azureus recognizes only magnet URIs with info-hashes in base32. For magnet URIs with info-hashes in HEX it just sits there a while, trying to find the torrent, and then fails to do so (apparently it interprets the hash as base32-encoded when it is really just HEX-encoded).
This feature has been fixed in version 4.3.0.1_b04
Last edited by trytenn; November 19th, 2009 at 04:10 PM. Reason: Sorry didn't read the hole thread.
Here's your answer:
The pirate bay uses magnet links in hex instead of base 32 like mininova.
The latest stable Vuze version (4.3.0.0) supports magnet links in base 32, but not in hex.
You will have to use the beta version 4.3.0.1_b04.
Other clients seem to support base 32 magnet links, but from my experience the Vuze beta is the only one currently supporting hex links.
I wrote a little script to convert magnet links from hex into base 32.
It simply takes the hex link as input and outputs the base32 link, so you should be able to use it with any torrent client supporting CLI input of base32 magnet links like this:
Don't forget to put "" around the magnet link!Code:CLIENT_COMMAND $(PATH_OF_SCRIPT/magnet_converter.py "HEX_MAGNET_LINK")
Usage examples:
Edit: It seems to work best when there are a lot of seeders. I had a few failures with less popular torrents. But the conversion itself seems to work correctly.Code:$ magnet_converter.py "magnet:?xt=urn:btih:ea53d1923abf55ae93276988275e29bc92a02be7&dn=Debian+GNU-Linux+Bible&tr=http%3A%2F%2Ftracker.openbittorrent.com%2Fannounce" magnet:?xt=urn:btih:5JJ5DER2X5K25EZHNGECOXRJXSJKAK7H&dn=Debian+GNU-Linux+Bible&tr=http%3A%2F%2Ftracker.openbittorrent.com%2Fannounce $ ./azureus $(magnet_converter.py "magnet:?xt=urn:btih:ea53d1923abf55ae93276988275e29bc92a02be7&dn=Debian+GNU-Linux+Bible&tr=http%3A%2F%2Ftracker.openbittorrent.com%2Fannounce") Starting Azureus... Suitable java version found [java = 1.6.0_0] Configuring environment... Java exec found in PATH. Verifying... ...
Last edited by KIAaze; November 19th, 2009 at 06:43 PM.
Excellent! Works great! Thanks!
Bookmarks