Not only would we need the version number, but if possible also the 'source': e.g. self compiled, our binary, Ubuntu, ... not sure how to enforce this though :(

We would require at cmake time to add a specific -D (but then we need this for any user as well :( ). Perhaps only enforce this in our src package (assuming that all packager just pick up the src package, and not a certain revision from our repo). Or is there an api/etc-something-file we could use to find which distribution was being used? For Suse we can look at /etc/SuSE-release (for older Suse), and /etc/os-release:

NAME=openSUSE
VERSION="13.1 (Bottle)"
VERSION_ID="13.1"
PRETTY_NAME="openSUSE 13.1 (Bottle) (x86_64)"
ID=opensuse
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:opensuse:13.1"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://opensuse.org/"
ID_LIKE="suse"

Similarly information about windows and osx version.

It's easy enough to add this on the STK side (once we figure out how to get it ;) ), I have just no idea about the server side.

Address used:
http://addons.supertuxkart.net:8080/upload/v1/

[error ] HW report: Error uploading the HW report.
[error ] HW report:

Bad Request (400)

Firewall? Or something wrong on my side?

The user count and OS data appears to be fine, but all other tables either show only one or no entry.

Currently every time the maint_graphics.py generates the report data, it removes all the old data and starts to process all the new data from scratch.
This is quite inefficient as it takes quite a lot of CPU power and memory (especially on low ram machines, cough digitalocean VPS).

A better solution would be:

1. Every time we run the generation script we will keep track of the last ID in the userreport table that was affected.
2. Every time the generation script is run it will only process data from the previous remembered ID to the current latest ID.
3. Handle user count for each device by looking up in the table to see if the device is already there https://github.com/supertuxkart/stk-stats/blob/master/userreport%2Fmaint.py#L48.
   Maybe another column which has the SHA1 sum of all the columns that identifies the device, so that we do not have to add non-clustered keys on all columns in the graphicsdevice table.
   But I am not sure which is faster, one column SHA1 sum (non-clustered key) OR all columns non-clustered keys (that uniquely identify a entry device).

As this code is forked from 0 A.D. it has some custom data version logic specific to it.
I think it will be better to reset all data versions checking in the code to 1. We can add our own specific data version checking later, if we change what kind of data is sent in different versions of STK.