Method of Reimplementing Client Tracking
Short, concise description of the idea
Bring back the Client Tracking feature, using a moderated list to prevent abuse.
Full description of the idea
The Client Tracking feature was disabled because protocol-savvy people were abusing it by putting in Arbitrary/Obscene Phrases.
My suggestion is this; for a client to be tracked it needs to be registered into a database/list. There's a quick form to fill out (Developer's Username, Client's Login String, Clients Community/Homepage, et...), and then a person either approves it or disapproves it.
Whenever a Client logged in, it would go through the normal Client login process, ignoring it if the string doesn't match up to a registered app.
To prevent hacking the Version number, there could be another argument added to the string to verify that it is indeed the developer who's come up with the string. Sort of like a password. If the Password got out and abuse started, the moderator could then just unauthorize the client string and the offending information would be gone.
So if I registered my Client Phoenix, then whenever I sent "Phoenix/1.8.6/ClientPassword" or "Phoenix/1.8.6-Carbon/ClientPassword" it would log the client stat, however "Phoenix-Carbon/1.8.6" or "Phoenix/You-Blow" wouldn't work.
An ordered list of benefits
An ordered list of problems/issues involved
An organized list, or a few short paragraphs detailing suggestions for implementation