Last Online mismatch between API data and webpage?

Sort:
stephen_33

Just noticed this for the following member:-

https://www.chess.com/member/pawn314159

The web 'last online' date clearly states Oct 26, 2022 wherever that data appears but the member's endpoint disagrees:-

https://api.chess.com/pub/player/pawn314159

"last_online":1667598759

When I decode the time integer I get this:-

tm_year=2022, tm_mon=11, tm_mday=4, tm_hour=21, tm_min=52, tm_sec=39, .....

i.e. Nov 4, 2022

I think I'm reading that correctly.

Tricky_Dicky

Looks a correct assessment. There is a discrepancy between the two data items,

stephen_33

I thought so but then the question is which of the two dates is the correct one, if either is?

Tricky_Dicky

I'd guess the latest and the Oct is a glitch.

ImperfectAge

I noticed that all players in club members lists now show as last online as Sep 24, 2022 at the earliest.  On the web.  Didn't check the API

stephen_33

Didn't we have a similar problem not long ago when members who'd been absent for years suddenly showed as having been online on the same date a few months before?

stephen_33

I messaged Ben (@bcurtis) about this but just noticed he hasn't been online for 3 days.

Ximoon

According to the web or the API?

stephen_33

"According to the web or the API?" - ha  😄

RYN_the_raper

there is a disruptancy between 2 of the data items

RYN_the_raper

discrepancy mb 

stephen_33

Reviewing some of my old, dormant topics and I think it was after creating this one that I was told accessing personal games via the app. registers as being 'online' on any webpage but this activty doesn't update the value in the endpoint.

And that's why we see these discrepancies I believe - anyone know?

* This reminds me of the fiasco with Daily timeout rates where the webpage value is calculated differently from the endpoint(s) - anyone know how the fix for that is coming along?