Today OGS is very slow for me. Is it the same for you?
This could be the reason for being able to see something that is always there but usually unseenā¦
There are many places on OGS where a strange text is presented before the right one.
Did you notice that tournament pages opens up showing different settings? Then, after a glimpse, they change to the actual settings.
Also in first @txwolf image his name is blue, not gold.
I donāt understand the reason for that, but looks to me like a double effort to load weird stuff and then the good one.
Conversely, itās probably a way to save time that I donāt dig.
My educated guess: If you use the OGS API to retrieve player data, there are many ārankā fields, each with a different value. Some of it are for ratings on different boards and time controls, but there are multiple conflicting generic ārankā attributes as well. Since ogs has been through a rank system change, I can imagine the amount of work needed to remove the old attributes and setup. Thus it probably makes sense to keep the old setup in place and replace the old rank data (fetched from an older code) with the new rank data through another API call.
Broadly, the rationale for this sort of thing happening is to load the page quickly, from locally cached (*) information if possible, then touch it up when the slower to arrive information gets there.
The āgame historyā list on our profile pages is the most obvious example. There is no cached information about that (OGS doesnāt try to remember all that in the browser) so the table is rendered empty to start with, then when eventually the server has compiled the list of your games, it loads them.ā
In the case of rank, it is likely cached. So you are seeing a very old version of what OGS thought the rank was before the server fetches the actual rank.
An obvious quesion is āwhy do I see a wrong rank if Iāve never seen that player beforeā. I donāt know the specific answer, but I can say that caches are wierd
GaJ
*: locally cached: when we see that information the first time in the browser, we save it in the browser, so we donāt have to ask the server again.