Transmission

Yeah, I can telnet to the port from my home computer but not from the one where the irc client is. The client is on a public server so it's possible it has been blacklisted by freenode due to abuse. There is, however, a web interface to freenode which works fine

But they do list the irc server as used for development discussions. It was unavailable last time I checked too or I wouldn't have posted though it looks like it is likely an issue with the system I'm trying to use to connect (which is odd as it usually runs completely open). Edit: Looks like possib...

It would make sense and help to minimize disk usage.

OK. Linked here:

http://perihelion.dyndns.org/numeric.diff

*** Connecting to port 6667 of server irc.freenode.net
*** Unable to connect to port 6667 of server irc.freenode.net: Connection
+timed out

Well, this doesn't seem to have generated much interest but I'm attaching the diff in case anyone might find it useful.

Or at least I would have except .diff and .txt are not allowed extensions. Anyone know what I can post it as?

I'm not really a big fan of storing passwords *anywhere* though (Though since transmission is single user and can be a unique password, not such a big deal but still...). Plus, ideally, it should be by default, not requiring a command line option.

I want a cookie for transmission-remote so that I don't have to keep on using the username:password thing on the command line (I actually have an alias that includes it but it's the principle). I'll probably code it myself but I wanted to see if anyone had any input on the idea.

Actually, both symbolic and hard links are supported by NTFS and there are tools for handling them, it just seems they don't want to use them in any way, shape or form. http://en.wikipedia.org/wiki/NTFS_symbolic_link However, they don't seem to be above cluttering my Windows 7 user folder with all ...

Different file structures doesn't necessarily mean that torrent shouldn't support it. There's sane ways to handle incompatibilities. That said, I wouldn't hold my breath. Was primarily thinking of when one uses absolute paths in the symlink and the effective impossibility of a sane conversion betwe...

Different file structures doesn't necessarily mean that torrent shouldn't support it. There's sane ways to handle incompatibilities. That said, I wouldn't hold my breath. The script thing was just a suggestion to the original poster as to how he might be able to handle the situation. Though I'm thin...

Possibly would be easier to just use a private tracker. Or just use a different protocol entirely.

But isn't it the case that DHT doesn't actually help with torrents you have active so turning it on or off whether you have active torrents or not is actually irrelevant. I think running DHT is more a thing to help keep the torrent network healthy. So if you don't want to pitch in, switch it off. I ...

If the process questioned in the first paragraph of this post were true, 99.99% of users would never connect remotely to their home computer via RPC, EVER!!! Why? Because most users only whitelist local IP addresses so, of course, source addresses are not examined by the RPC code as they would all ...

There's no reason the torrent spec couldn't be expanded to allow for storage of symlinks but that might cause issues between different systems (though no doubt there are already a few issues like that unless the spec is very tight). Maybe consider a script which creates a new dir structure where rea...