Magnet/infohash hex vs base32 encoding

[benv666]

Hej folks,

Since Piratebay closed their tracker for good, the magnet/infohash support becomes even more important.
However, they decided to use hex encoding according to the spec.

When I try to add a magnet link through the web UI (deluge v1.2.0-rc3), the infohash button is grayed out. (does anyone know why?)
Next I tried the gtk ui, but the ui refuses to accept my link. I guess because of then encoding, but since it gives me no feedback I have no idea what goes wrong.
I tried the patches attached to this ticket but they don't help.

Does anyone have a suggestion?

BenV

[dack]

I have also observed this problem. However, it appears to work correctly if you use the GTK interface's infohash tab and enter the plain hex hash as well as a tracker in the second box. It doesn't seem to work without the tracker or if you enter the full magnet uri.

Another related issue - how can a URI be passed to the deluge for downloading from the browser? You can supply a local torrent file as an argument to deluge, but that doesn't work for http or magnet URIs.

[andar]

I've fixed an issue where adding hex encoding magnet links would not work properly in the add torrent dialog.

Deluge does support both formats, so if you turn off the Add Torrent Dialog and add the link to a running session: deluge <magneturi> it will add it to the session properly.