First of all: if the main tab will contain either Downloads (leeches) or Uploads (seeds) you can just label that tab "Transfers"...

Then, I was thinking about the trouble I'm having (and I think even others) with some peers: KTorrent bans them if they send corrupted data (I activated the log plugin).

I think it would be best if you change the policy of banning such peers. For example if the peer send 3 corrupted chokes in 5 minutes you ban it for 5 minutes then retry. You can even add a policy manager inside "Configuration" window, allowing users to choose their own policy...

I say this because I've notices that KT bans them as soon as they send a (one) bad choke! That's a very pessimistic policy! KT bans peers that send me about 10 chokes/minute!!! It's useless to say that this policy is a big SLOOOOOOWWWDOWN...

Can you set it before 1.2 release?

First of all: if the main tab will contain either Downloads (leeches) or Uploads (seeds) you can just label that tab "Transfers"...

We have planned to separate 'Downloads' and 'Uploads' tabs some time in the future, so I guess there's no need changing that now

As for the banning policy, we only ban peers which send 3 bad chunks not 1. But, I have also noticed KT banning some peer right after 1 bad chunk so I guess there could be some bug present. I will check it out right away.

Ivan wrote:We have planned to separate 'Downloads' and 'Uploads' tabs some time in the future, so I guess there's no need changing that now

Ah, ok then...

Ivan wrote:As for the banning policy, we only ban peers which send 3 bad chunks not 1. But, I have also noticed KT banning some peer right after 1 bad chunk so I guess there could be some bug present. I will check it out right away.

I've noticed that too... however it seems like the peer which I am downloading from sends many chunks but most of them is corrupted... so I don't think that's really a problem about KT but about the seeder. However the problem with the IP filter seems to exist...

Ivan wrote:

First of all: if the main tab will contain either Downloads (leeches) or Uploads (seeds) you can just label that tab "Transfers"...

We have planned to separate 'Downloads' and 'Uploads' tabs some time in the future, so I guess there's no need changing that now

As for the banning policy, we only ban peers which send 3 bad chunks not 1. But, I have also noticed KT banning some peer right after 1 bad chunk so I guess there could be some bug present. I will check it out right away.

I think I changed that to 1.

Think about it : The data is sent over TCP, so it is sent over properly, so what the other side sends us is wrong. There are 2 ways the data can be wrong :

- A bug in the client
- Payed idiots who maliciously send bad data to prevent people from downloading in a decent way

Seeing that the first option is not that likely (most people use stable versions). Most of the time it will be option 2, and we just ban them.

Well, I don't mind banning client after 1 bad chunk. I block them manually when I notice a first bad chunk warning. I suppose that's why I've overseen this 'bug'.

Maybe we could make this configurable via settings, leaving the option to the user to change number of bad chunks before ban... But, seeing that no more features will be added for 1.2, it would have to wait.

George wrote:- A bug in the client
- Payed idiots who maliciously send bad data to prevent people from downloading in a decent way

I would add:

- Clients with troubles with their Internet line

George wrote:

Ivan wrote:

First of all: if the main tab will contain either Downloads (leeches) or Uploads (seeds) you can just label that tab "Transfers"...

We have planned to separate 'Downloads' and 'Uploads' tabs some time in the future, so I guess there's no need changing that now

As for the banning policy, we only ban peers which send 3 bad chunks not 1. But, I have also noticed KT banning some peer right after 1 bad chunk so I guess there could be some bug present. I will check it out right away.

I think I changed that to 1.

Think about it : The data is sent over TCP, so it is sent over properly, so what the other side sends us is wrong. There are 2 ways the data can be wrong :

- A bug in the client
- Payed idiots who maliciously send bad data to prevent people from downloading in a decent way

Seeing that the first option is not that likely (most people use stable versions). Most of the time it will be option 2, and we just ban them.

Depending on what is transfered, TCP cannot be relied on completly.
The crc check is not fail-safe. Before programs started to md5 check files, There was a big chance of getting errors on high compressed video sent over tcp.
I would go for default 2 and user-editable.