Does anyone know why the Zwifters Nearby list does not display the actual speed? Since we don’t know the other riders’ weight, size, age, or gender, W/kg isn’t really helpful. The actual speed, meanwhile, does help. Just saying.
I reckon it is a technical hurdle - at some level w/kg requires less information to be extracted related to the data objects which are the other riders. The weight is static, the power is one discrete value that does indeed change but comes directly from the other rider’s input to the game (from their trainer - it doesn’t need to be calculated) so it’s just one value that even if a bit stale is easy to work with…speed is being calculated for each rider (and presented to that rider) from that power but also based on the terrain they are on at a given instant and the rest of the physics model - the game engine is already working hard to come up with that to display it and render the impact of it just at the client end (note that all of that keeps working even if you lose connectivity) - to rapidly and reliably make it available upstream on the server side to (and from) everyone nearby could be…well…harder than “just” w/kg. It’s already obsolete the second you calculate it, so you’ve got to keep a firehose of re-calculated speeds going up to the server and make it available for the clients of everyone around you to consume. Getting “just” the power and position coordinates may be all that is practical. I’m not saying it can’t be done, just that to do it accurately might be trickier or more expensive computationally at one end or the other than you might think, considering where the different code is actually running.
[To be clear - it could be straightforward if you started out designing it from scratch to have the data available - I’m saying that with the current code which is obviously pretty firmly entrenched it could be pretty tough]