Does tracker list whether a peer is seed/leech?

[RedRansom]

Then he want to know if he can get peers ip adress without connecting to tracker?
I think this is impossible for private trackers cuz all torrents creating by uploaders which checking "private torrent" option at their client than this makes this file only for the tracker member than this makes DHT pointless but for public tracker DHT is optional and usually on but still you need to connect to tracker by your client and i want to say if someone could have ip adress without connect to tracker this cant imaginable and this will damage the private torrenting and bittorrent wold

[tutipute]

When a peer contacts a tracker to get a subset of the peers in the swarm, my understanding is that the tracker basically just returns a list of IP addresses (according to http://wiki.theory.org/BitTorrentSpe...acker_Response).

Is it possible to get the tracker to also tell me whether each of those peers is a seed or leech? My understanding the seed/leech status is only learned from direct contact with another peer, but was wondering if it could also be learned from the tracker.

... have fun hunting ppl

@tutipute he is OBVIOULSY making a research paper..
https://filesharingtalk.com/vb3/f-fil...75#post2949650
yeah sure....

help him poor kid

LOL! Shoot him a b***e invite then...

[NYTReader]

Hi everyone:

Thanks for the quick replies (I forgot how quick this board is so sorry for taking a few hours to get back!).

First let me say no way am I working for an interdiction or monitoring company hired by any content owner. I am just trying to understand the BT protocol a bit better for some of my own research.

Sorry my original posting was a bit cryptic. I am not interested in coding up a new tracker but rather want to know if there was a way as a peer to get the tracker to let me know leech/seed status of the IP's I am given. I think the consensus is that there is not.

Just out of curiosity does anyone know why this is so? The added overhead would be pretty small (an extra bit I imagine). I doubt this was for legal reasons given the history of BT (plus I think it does not matter whether you are seed/leech: as long as you are allowing others to upload from you, the content guys will go after you, at least here in the US).

Thanks again for all of the responses.

[tutipute]

Just out of curiosity does anyone know why this is so? The added overhead would be pretty small (an extra bit I imagine).

There many questions that can be asked regarding the BT protocol. Many software developers have already altered the protocol to fit far more complex sharing/community based Software. Yet, the question that should be asked is why are you so into this specific feature?

[yayyyyyy]

Just out of curiosity does anyone know why this is so? The added overhead would be pretty small (an extra bit I imagine). I doubt this was for legal reasons given the history of BT (plus I think it does not matter whether you are seed/leech: as long as you are allowing others to upload from you, the content guys will go after you, at least here in the US).

Thanks again for all of the responses.

when you DEVELOP something the question you have to ask yourself is: "is this thing usefull?"

if all the developers would live with the question: "why isn't this thing usefull? we would have a shitload of UNFINISHED PROJECTS loaded with tons of crap that nobody will ever use...

how would be torrent protocol benefit from such an information??? what's the point???
Trackers are there only to let you know that someone is involved in a certain torrent hash, all the rest MUST and IS DONE client side... I see no benefit at all having such an additional information coming from the tracker...

btw, most current tracker implementations can be "exploited" in a way opposite to what I think you want to do (I'm still convinced you are involved into antipiracy and all that crap):
if you report yourself as a seeder (complete flag sent) to the tracker, the tracker WILL NOT give you ip addresses of other seeders... you will get only leechers ips...

on very small swarms you can do 2 announces:
first one as seeder, second one as peer... then compare the resulting ips.... and you are done... the ones missing in the second announce are seeders

but that works only on very little swarms (20 total peers?) and might still be incorrect if some client is "not connectable" as those will be never reported to you

happy hunting

[NYTReader]

Thanks again for the replies. I understand the point about not wanting to burden the tracker; that makes sense.

And my apologies again if my posts are on a suspicious topic: it really is just academic curiosity on my end.

[tutipute]

Thanks again for the replies. I understand the point about not wanting to burden the tracker; that makes sense.

And my apologies again if my posts are on a suspicious topic: it really is just academic curiosity on my end.

Well, we are all waiting for the research link once its done...

Spoiler: Show

[NYTReader]

Funny: I like the older one too,

[yayyyyyy]

And my apologies again if my posts are on a suspicious topic: it really is just academic curiosity on my end.

wish to see such research result published here... it's passed a year since you started researching about the timing needed to get a dubbed release published, gotta be a very big research