Transmission

Not sure why you post this here, but maybe the file is corrupt. Try verifying the torrent.

I really like the 'pieces' bitfield in the rpc, and I'm having the idea of not just showing if a certain piece is downloaded or not, but also to show how available it is in the swarm. This could be the number of peers who are offering this piece, but it could also be something more abstract, like a ...

Whoops. Sorry for asking stupid questions. And thanks for the fast response.

I just upgraded to 1.61 and tried to adjust trcli, but I get a HTTP error: 409 - Conflict. I couldn't find any documentation about this. Any clues?

Should features not be added?
Yes, they should. As I said, I completely understand that a protocol cannot stay the same while the software is evolving.

Don't worry about supporting older versions, then. Users will accept being told "you need to upgrade" a lot easier than they will being told ...

I think you're overreacting. There's only been one set of incompatible changes to the RPC spec, and that's from 1.52 to 1.60. As you're probably aware, the reason "uploadLimitMode" was changed was to keep in sync with 1.60's new features.
Yes, maybe I am overreacting a little. Currently there are ...

According to the rpc specs "uploadLimitMode" is removed from the protocol in version 1.60. Maybe the Ubuntu 1.51-package features patches from this version, at least I don't have a better explanation.

The main problem are the ongoing changes in the rpc protocol which transmission-remote-cli wasn't ...

Sorry for the delay, the e-mail notification doesn't work or I'm too stupid to use it.

You error message doesn't have to do anything with libraries, it is caused by a protocol change from transmission 1.40 to 1.50.
Concidentally, I just fixed this bug, so it should work now.

I still don't know how you got this error message. I just created 300 torrents and added them all, but everything was fine. Except a really high cpu load, but transmission-remote-cli was still usable.
I'm sorry, but if I cannot reproduce your error, I cannot fix it.

That's a strange error. And you have over 237 torrents! For some reason, the response from the daemon breaks in the middle and a new response is started.
Anyway, I don't have any idea what could cause this. At the moment, I think the bug must be either in transmission-daemon or in some Python module ...

Ok, thank you. I'm gonna remove the (few) lines regarding webseeds until this is working.

Hello again.

I have yet another question: How am I supposed to handle webseeds? I created a test torrent, but the webseed list from the daemon is always empty. Here is a sample request:

{
'tag': 77,
'method': 'torrent-get',
'arguments': {
'fields': [..., 'webseeds', ...],
'ids': 23 ...

I would answer that, but I'm currently too busy wishing that the curses interface had activity filtering... :wink:
As I'm totally open for being blackmailed, I just implemented your filter list. :)
No, I actually had second thoughts about it and found that it's a quite trivial thing to do. At ...

Sorry for not answering, for some reason I didn't get a notification email. (?)

I just had to pop in and say "thanks". This is exactly what I need to run transmission off my headless home server.
The latest version is running very well for me. In fact it's quickly becoming my remote viewing ...

Thanks for your fast reply. libtransmission.h answers this question and some I'm gonna have in the future.