Chris Fairfield (thorshammer) wrote in suggestions,
Chris Fairfield

Method of Reimplementing Client Tracking

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

  • Return Client Tracking,Which helps Developers know:
  • +How Quickly People are Updating their Clients
  • +Which Operating System People Are Using (Mainly a Mac thing, are they using Classic or OS X)
  • +How Sastisfied People Are in Comparison to Other Clients
  • +And Finally, How Many People are Using the Client
  • Prevents Abuse of System
  • An ordered list of problems/issues involved

  • Would need someone to Moderate The List (Note: This is something I'm willing to do)
  • Someone could hack the version number to say obscene things (If the Password system isn't used)
  • An organized list, or a few short paragraphs detailing suggestions for implementation

  • I'm not quite sure how the system works, but it sounds like you wouldn't need to add in much. Maybe a function that checks to see if a client is authorized, if it is it returns the password, and then it checks to make sure the Password matches. If the Password matches, then it proceeds with the normal logging code, if it doesn't then it ignores it.
  • Tags: clients and apps, statistics, § historical
    • Post a new comment


      Anonymous comments are disabled in this journal

      default userpic

      Your reply will be screened

      Your IP address will be recorded