I make my congratulation to the devs of KTorrent: version 1.2 seems to have many fixes and also many improvements compared to version 1.1.

I would like to suggest a new feature: super-seeding. Almost every BitTorrent client has such a feature implemented (BitTornado, BitSpirit, Azureus... et cetera). It's very useful for releaser with a connection such as DSL...

Thanks for KTorrent!

We will put it in the version after 1.2, to late for new features now.

Ok... there's a roadmap? When will be released the v1.2?

Another thing: where can I get some information about programming plugins for KTorrent (I'm a dev too) and what IDE did you use to write it?

axelgenus wrote:Ok... there's a roadmap? When will be released the v1.2?

End of the month.

Another thing: where can I get some information about programming plugins for KTorrent (I'm a dev too) and what IDE did you use to write it?

Download the code and look at the existing plugins. Most code (but not all) has doxygen comments, so you can use doxygen to generate HTML docs.

And if that isn't enough send me an e-mail or post a question on the forum.

I use KDevelop for an IDE (when I'm writing C++ that is, hacking low level C code is best done in vim, but I only do that at work).

Does KTorrent work at all when a peer is SuperSeeding?

The peers tab should have the peer superseeding listed as a peer with 0% (or a % matching 1 chunk), but I cant se anyboby with that low %.

A SuperSeeder says it has zero cunks to the tracker, and when a peer connect it says it just got one.

Pär H wrote:Does KTorrent work at all when a peer is SuperSeeding?

Why not, the other side is doing the SuperSeeding.

The peers tab should have the peer superseeding listed as a peer with 0% (or a % matching 1 chunk), but I cant se anyboby with that low %.

A SuperSeeder says it has zero cunks to the tracker, and when a peer connect it says it just got one.

Everytime the superseeder sends a HAVE, it's percentage will increase.
There is no message to tell you to not have a chunk anymore.