Roderick, everyone...
Again I am looking for numbers to estimate how big our community roughly but it will always be a gamble to a large extend.
...
The 500 users was based on the IP numbers from Netlabs. But how accurate that is ? But I never stated we have 500 private users left. Read the other postings for the rest of the details...
So why don't we set up a honey-pot of sorts and use a different approach to uniquely identify the hardware that's running OS/2?
My understanding is that ANPM does exactly that. They use dmidecode to pull an OEM string that identifies the hardware, my understanding is that this is the UUID field value (not 100% sure, but someone could verify).
So here is what that looks like on my machine:
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: MSI
Product Name: MS-7640
Version: 1.0
Serial Number: To Be Filled By O.E.M.
UUID: 00000000-0000-0000-0000-6C626D50A7A8
Wake-up Type: Power Switch
SKU Number: To Be Filled By O.E.M.
Family: To Be Filled By O.E.M.
Take a look at the full dmidecode dump (see attachment). What would simplify this is having a front-end web page that spells out how the end-user should do this, and we're talking literally a simple 1-5 step process, or simply accepts the UUID value that the user extracts out of the dmidecode dump.
Heck, dmidecode has an option to literally pull just the UUID, that being: "dmidecode --string system-uuid".