This one's a bit tricky; I can imagine it may need a change to backend database storage. It's useful enough to me and I imagine to future chess.com internal use that I'm going to ask for it anyway.
"joined": 1178556600, // timestamp of registration on Chess.com
I would like to see:
"closed": 1188556600, // timestamp of account closure on Chess.com
The advantage to me is that when calculating results for incomplete matches that have passed a deadline, I can tell when they were closed and not have to guess based on last_online time ... since people do sleep. A self-closure time and last_online time should be close. An abuse or fair_play_violations closure may not be.
For chess.com, it provides a timestamp after which no moves can have been played; if desired in progress games can be timed out immediately and there is a record of when someone left, and if staff access an account (which seems to upset last_online time) there remains a record of when the account owner last accessed the account.
In he case an account is reopened (which I have seen for self-closures, closures for abuse and fair play violations closures) the "closed" timestamp should be deleted and no longer provided.
A potential problem exists were account profiles and/or stats are cached with the account considered closed, but the addition of a "closed" timestamp doesn't worsen that case.
My particular impetus for wishing to know when a particular account was closed was for TMCL: one user's account was closed about the TMCL deadline. The last_online time preceded the deadline, but the exact time of closure is a mystery.
This one's a bit tricky; I can imagine it may need a change to backend database storage. It's useful enough to me and I imagine to future chess.com internal use that I'm going to ask for it anyway.
The player profile endpoint:
https://www.chess.com/news/view/published-data-api#pubapi-endpoint-player
... has:
I would like to see:
The advantage to me is that when calculating results for incomplete matches that have passed a deadline, I can tell when they were closed and not have to guess based on last_online time ... since people do sleep. A self-closure time and last_online time should be close. An abuse or fair_play_violations closure may not be.
For chess.com, it provides a timestamp after which no moves can have been played; if desired in progress games can be timed out immediately and there is a record of when someone left, and if staff access an account (which seems to upset last_online time) there remains a record of when the account owner last accessed the account.
In he case an account is reopened (which I have seen for self-closures, closures for abuse and fair play violations closures) the "closed" timestamp should be deleted and no longer provided.
A potential problem exists were account profiles and/or stats are cached with the account considered closed, but the addition of a "closed" timestamp doesn't worsen that case.
My particular impetus for wishing to know when a particular account was closed was for TMCL: one user's account was closed about the TMCL deadline. The last_online time preceded the deadline, but the exact time of closure is a mystery.
Thanks for your consideration,
Giles