Open GoogleCodeExporter opened 9 years ago
Possibly, although it would have to wait until after my exams. I can't make up
my
mind if this is bloat or not. It also depends if I could take the .torrent
creation
code from MonoTorrent and integrate it without too much hassle/size increase.
Original comment by AlanF...@googlemail.com
on 16 May 2009 at 1:34
Maybe there is way to call the [transmissioncli -n <source> -a <url> -r]
through ssh.
Original comment by liuzh...@gmail.com
on 16 May 2009 at 2:59
Or ask charles to implement the torrent creation into daemon. So create torrent
through rpc.
Original comment by elso.and...@gmail.com
on 18 May 2009 at 11:17
Original comment by elso.and...@gmail.com
on 23 Jan 2010 at 10:39
it will be very if you will do it. thanks
Original comment by aladjev....@gmail.com
on 21 Jan 2011 at 10:06
Personally I thinks that would be another major improvement. Currently there's
no easy way in Windows to create a torrent for transmission that me or a Google
search is aware of - "Transmission Remote" would be the only one so far.
In OSX it seems to be pretty easy
http://filesharefreak.com/tutorials/transmission-creating-seeding-torrents-on-ma
c/
Original comment by bulgar...@gmail.com
on 30 Jan 2011 at 1:17
bulgarion: the main problem is: this program is only a "remote controller" for
transmisson (daemon). Pointless create the torrent at local computer, the
transmission can be far away.
Original comment by elso.and...@gmail.com
on 30 Jan 2011 at 10:44
Correct me if I'm wrong on this design:
I use transmission on my Qnap NAS. I want to seed a group of files from there,
and I need to upload a .torrent to a tracker. Normally I should use the cli
interface for creating a torrent, transfer it to my pc and upload it to the
tracker (and then start seeding); transmission-remote could ease this scenario
by allowing to create a torrent reading the destination download directory,
choosing the files to seed, exporting the .torrent and auto-adding it to the
download (seed) list.
Original comment by bulgar...@gmail.com
on 31 Jan 2011 at 9:31
Original issue reported on code.google.com by
liuzh...@gmail.com
on 16 May 2009 at 3:09