Treferwynd / transmission-remote-gtk

Automatically exported from code.google.com/p/transmission-remote-gtk
GNU General Public License v2.0
0 stars 0 forks source link

In remote client there is no "Copy magnet link to clipboard" intem in context menu #220

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
Right-click on any torrent. 

What is the expected output? What do you see instead?
I would expect item "Copy magnet link to clipboard" (transmission-gtk has such 
an item). 

What version of the product are you using? On what operating system?
transmission-remote-gtk 1.1 on Fedora 17.

Please provide any additional information below.

Original issue reported on code.google.com by van.de.b...@gmail.com on 16 Dec 2012 at 6:40

GoogleCodeExporter commented 9 years ago
I can't see any way to get the magnet URL in the RPC document, so there's not 
much I can do: https://trac.transmissionbt.com/browser/trunk/extras/rpc-spec.txt

Most, but not every piece of information in the GTK client is exposed in the 
RPC. Let me know if you find out how and I'll consider implementing it.

Original comment by a...@eth0.org.uk on 2 Jan 2013 at 8:43

GoogleCodeExporter commented 9 years ago

Original comment by a...@eth0.org.uk on 2 Jan 2013 at 8:47

GoogleCodeExporter commented 9 years ago
I am not sure about capabilities of RPC, but it seems remote client has all the 
information and can (re)create magnetic link. I just copied magnetic link from 
(non-remote) transmission client. It looks like:

magnet:?xt=urn:btih:<hash>&dn=<display name>&tr=<tracker address>

<hash> and <tracker address> are visible in torrent properties accessible by 
right-click on torrent in remote client; <display name> is present in the list 
of torrents. 

<display name> and <tracker address> should be URL-encoded (e. g. space is 
replaced with %20, colon with %3A, slash with %2F, etc). If there are more than 
one tracker, multiple "tr" parameters should be specified. Since <hash> 
consists of only hex digits, there is no need in encoding them, but probably 
you already have a some function to create a link from address and set of 
parameters. 

Thus, a magnet link can be easily (re)constructed.

Original comment by van.de.b...@gmail.com on 2 Jan 2013 at 9:09

GoogleCodeExporter commented 9 years ago
BTW, I found "magnetLink" in section "3.3.  Torrent Accessors" in the RPC 
document you pointed: 
https://trac.transmissionbt.com/browser/trunk/extras/rpc-spec.txt

Does it help?

Original comment by van.de.b...@gmail.com on 2 Jan 2013 at 9:15

GoogleCodeExporter commented 9 years ago
I saw that, but it's a number so I think it just tells you if it came from a 
magnet.

So I may look at building the URL sometime then, that should be possible. I 
don't know much about them as I rarely use them, but I understand what you're 
saying.

Original comment by a...@eth0.org.uk on 2 Jan 2013 at 9:19