This is a stopgap until/unless we have an API we (developers) can consume.
This should be an easy one, very incremental change to the way logging is done today, by resolving the numeric “user id” to their human, identified “nameplate”.
Today, the logs look like this:
===================
[16:07:13] NETWORK:Heard area message from 73677 (Woohooo what a ride!!!)
[16:11:30] NETWORK:Heard area message from 73677 (Did I aready say that I <3 ZWIFT!?)
==> [16:15:33] NETWORK:Player 73677 joined the world
[16:16:06] NETWORK:Received broadcast segment results for segment 1065066326 with a time of 1410.24 for user id=73677
[16:16:09] NETWORK:Received broadcast segment results for segment 5353681768 with a time of 43.25 for user id=73677
[16:16:09] NETWORK:Received broadcast segment results for segment 9634088118 with a time of 245.27 for user id=73677
===================
Resolving the users in the logs so parsing them gives you a human readable name could be as simple as:
===================
[16:07:13] NETWORK:Heard area message from 73677 (Woohooo what a ride!!!)
[16:11:30] NETWORK:Heard area message from 73677 (Did I aready say that I <3 ZWIFT!?)
===> [16:15:33] NETWORK:Player 73677 (J.Smith (ZTR-A) joined the world
[16:16:06] NETWORK:Received broadcast segment results for segment 1065066326 with a time of 1410.24 for user id=73677
[16:16:09] NETWORK:Received broadcast segment results for segment 5353681768 with a time of 43.25 for user id=73677
[16:16:09] NETWORK:Received broadcast segment results for segment 9634088118 with a time of 245.27 for user id=73677
===================
This would allow us to parse out the numeric user_id and map it to things like chat, race results and other useful bits of information tracked in the logs.
If we can get this information programmatically, that is preferred, but today, we cannot, so we rely on log scraping and parsing to give us some useful data.