On the subject of dots on a map, I still think consideration should be put in the direction of a thin client.
By this, I mean a downloadable executable, which catches data from the pitwall server and displays it in it's own fashion as an alternative to a browser reloading. Simple struct data must surely be far smaller in bytes than an HTML page, and no so disimilar to any other API application.
If the manner of this data transmission was documented thoroughly, then third-parties could write them giving users a choice. Some may enjoy the dots-on-a-map view, but some may prefer alternative interfaces. I myself would prefer a trackside view with cars whizzing past. Some may not want the hassle and continue to use the web interface. However it's done is of no consequence, the server just outputs a collection of bytes and the client assembles that into something usable for the player.
As it stands, it could already be achieved through scraping the web pages on refresh, but that seems awfully wasteful of bandwidth when the amount of actual relevant data is tiny compared to the size of a whole page. (EDIT: This would also be in contradiction to Rule 11.)
Just a thought.
