Platform specific client information.

[ceed]

Hi,

I would like to see platform specific client information in Transmission. As it is now the only thing I see is "Transmission 1.xx", not what OS is runs on. I would like to see something like "Transmission 1.xx Win" or even "Transmission 1.xx Linux/GTK".

//ceed

[livings124]

Why is that? The core is the same for all clients.

[ceed]

Why is that? The core is the same for all clients.

Because I am curious and would like to be able to see this information. Also, sometimes there's a pattern in behavior from software which depends on the underlying platform specific network stack. For instance for Opera the browser the client information (called user agent) indicates version and which OS it's running on like this: Opera Mail/10.00 (Linux)

//ceed

[livings124]

We are not going to be changing our identifier information. Trackers would need to make adjustments, etc. It's not worth it.

[jch]

We are not going to be changing our identifier information. Trackers would need to make adjustments, etc. It's not worth it.

You could keep the initial segment of the id unchanged, and just embed platform information further down.

[livings124]

Could still confuse some tracker's cheat algorithms, that expect the remaining values to be random - I know that those algorithms are pretty complex and don't want to risk it. There really is no benefit to including this info.

[ceed]

Could still confuse some tracker's cheat algorithms, that expect the remaining values to be random - I know that those algorithms are pretty complex and don't want to risk it. There really is no benefit to including this info.

I respectfully disagree. Well, how could I not since I started this topic?

//C

[livings124]

You respectively disagree with the fact that sending this info would piss off trackers and give no tangible benefit? Please, explain.

[jch]

You respectively disagree with the fact that sending this info would piss off trackers and give no tangible benefit? Please, explain.

I disagree with the notion that it would confuse trackers. A smart encoding of peer platform within the peer id could very well be upwards-compatible.

I hold no opinion on the alleged benefits.

[ceed]

You respectively disagree with the fact that sending this info would piss off trackers and give no tangible benefit? Please, explain.

Well, there's disagreement on the "piss off" factor in this thread, so I am not capable of determining if this added information would "piss off" trackers or not. If it did, it could be a problem. If not, well then it wouldn't (doh!

I explained earlier in this thread why I think it could be valuable, one reason being that I am curious. If that's not tangible benefits in your opinion then that's your opinion and I will of course accept it as such. I would also like to thank you for a great BT client. I wish it success on all platforms regardless of information submitted to the tracker

//C

[ceed]

Hi,

I just noticed that uTorrent has platform specific information available for their Mac version. It says: "uTorrent Mac 0.9.2". So obviously they have found a way to not irritate the trackers with this added information.

//C

[livings124]

They have always had this; we would have to change how we report.

[Rolcol]

Hi,

I just noticed that uTorrent has platform specific information available for their Mac version. It says: "uTorrent Mac 0.9.2". So obviously they have found a way to not irritate the trackers with this added information.

//C

They have always had this; we would have to change how we report.

µTorrent for Mac uses the UM identifier while the Windows version uses UT. Their Mac client has always identified itself as UM. Transmission's cross-platform core, libtransmission, identifies itself as TR for each client and there would need to be many changes if your request were to be implemented, and, as livings124 is saying, this would cause tracker operators headache for having to add each new client on the allow list. They may just end up banning the client all together. The Bittorrent specification states that a client returns its version in a 20byte message. Following the Azureus ID style, the last 12bytes need to be random to conform to the spec. It'd be fun for only a few times to know what OS they run but it's not important. It's more headache than it's worth.

http://wiki.theory.org/BitTorrentSpecification#peer_id