Opened 15 years ago

Closed 15 years ago

#130 closed Enhancement (invalid)

client identification in peer list

Reported by: jah Owned by: somebody
Priority: Normal Milestone: Sometime
Component: Transmission Version: 0.6
Severity: Trivial Keywords:
Cc:

Description

it comes up as 'unknown client'. We should at least acknowledge our competition.... :)

Change History (5)

comment:1 Changed 15 years ago by jpiper

if it was actively being developed, then i might call it a competitor ;)

comment:2 Changed 15 years ago by livings124

  • Resolution set to fixed
  • Status changed from new to closed

Done in [773].

comment:3 Changed 15 years ago by mechanic

  • Resolution fixed deleted
  • Status changed from closed to reopened
  • Summary changed from Add bits on wheels to peer list to client identification in peer list

some mainline and ABC clients are showing as unknown: A310--00 M4-20-4- M4-20-7-

here's a few references for many more identifications: http://azureus.cvs.sourceforge.net/azureus/azureus2/com/aelitis/azureus/core/peermanager/utils/BTPeerIDByteDecoder.java?revision=1.26&view=markup from mainline client: BitTorrent/ClientIdentifier?.py

comment:4 Changed 15 years ago by livings124

[787] fixes the problem with the mainline identification.

comment:5 Changed 15 years ago by livings124

  • Resolution set to invalid
  • Status changed from reopened to closed

Open tickets for specific client identification. Keeping this open won't really accomplish anything.

Note: See TracTickets for help on using tickets.