So I reloaded the infowidget. I noticed that you use a different terminology than what I have seen in other places.


Leechers: people who download but do not seed
Peers: people who have not completed downloading
Seeders: People who have finished Downloading and are uploading completed file

By what I see you call Peers, leechers. But on your list seeders get counted as peers. It is important to know how many Seeders there are to how many people are downloading. This is especially important when seeding. If you notice 30 people downloading and one person seeding you might want to give priority to that file.

The only way to know who is leeching is to figure out if the person does not seed. Or if they cap their uploads while downloading. But the latter would not work because I only have 500 kbips up to the 4 or so mbips download. and even then I have to cap my upload when I am trying to use the net to 20-30 Kbyps. Otherwise I can not browse the web.

Too bad there is no way to detect leechers.

What I want to know is what is you terminology for capped and snubbed. cause on one file I am connected to 14 people and only 1 is not capped or snubbed. Is there anyway to adjust this option?

I'm not sure where did you get that idea about Leechers != Peers...

If you look closer, on InfoWidget you'll find "Leechers" and "Seeders" meaning - People who are currently downloading the file and partially distributing and people who have completed the download and are fully distributing the file(s). You may have seen "Peers" label in PeerView or ChunksView and that label refers to both leechers and seeders. You can make a difference by looking at 'Availability' column which shows percentage of download completion.

What I want to know is what is you terminology for capped and snubbed. cause on one file I am connected to 14 people and only 1 is not capped or snubbed. Is there anyway to adjust this option?

I think you mean 'snubbed' and 'choked' not 'capped', right? You may want to check out this document, I'm sure it'll explain better than I would.http://wiki.theory.org/BitTorrentSpecification

I understand how you are wording it. But what I am saying... and this comes from your average moron who has bounced around several torrent apps looking for greener fields........ Other apps say a peer is anyone downloading and a seeder is a person not downloading but still uploading.... a leecher is a person who does not seed. You know leech.... small creature that sucks blood off animals and drop off when full.

I was trying to make a point about making availability clear when not running infowidget. for instance Azureus has a peer column and a seed column. and it states something like "1(3)" which would mean I am connected to 1 of 3 possible in that column. You have a column that has peers. And for the sake of asking the peer column says "14" So without loading extra resource taking bits.... does it make clear that the download is going slow because:
a: you are connected to all 14 seeders
b: you are connected to 14 people and there is no one seeding
c: you are connected to 14 people there maybe some seeder but they are not connected to you so wait your turn.

I download Japanese Television shows. And generally there will only be 4 or five people at a time getting the show.... and I can sit for days not downloading anything because there are no seeders on at this time.... so with something that tells me that there are 5 people. I have to load up infowidget to find information that could easily be made available by the use of an extra column or so.

Ivan wrote:I'm not sure where did you get that idea about Leechers != Peers...

If you look closer, on InfoWidget you'll find "Leechers" and "Seeders" meaning - People who are currently downloading the file and partially distributing and people who have completed the download and are fully distributing the file(s). You may have seen "Peers" label in PeerView or ChunksView and that label refers to both leechers and seeders. You can make a difference by looking at 'Availability' column which shows percentage of download completion.

What I want to know is what is you terminology for capped and snubbed. cause on one file I am connected to 14 people and only 1 is not capped or snubbed. Is there anyway to adjust this option?

I think you mean 'snubbed' and 'choked' not 'capped', right? You may want to check out this document, I'm sure it'll explain better than I would.http://wiki.theory.org/BitTorrentSpecification

Sorry for forgetting earlier but thanks for the read. That was great. Took me a while to absorb it but it really explain some fuzy bits. But still its seems like there should be a better way to communicate snubbed than just assuming that since I have not gotten a reply they but be snubbing me. And it sucks that I am connected to the only 14 people available and I am snubbed by all of them.


ce la vie

I hate to be pedantic, but I couldn't help noticing that what you are referring to is, ironically, 'semantics', not symantics.

As for the splitting of peers into 'seeders' and 'leechers', I think that would be a good idea, as it would enable one to judge the quality of a torrent from the torrent list without having to look at the infowidget for each torrent individually. It's not a huge deal, but it is something I would advocate.

You know its funny how many ways things can be spelled in the english language. And no matter what someone is going to point out something when the understood what was being said. But you would not have been able to point that out if we had the same discussion face to face. BTW I still say wharehouse after being bugged a million times about it being spelled warehouse. Odd aint it.

But I am glad you understand what I was getting at. Its just a little convience that saves a tad bit of proccessing power.