I'm currently using the SRC v1 API to construct WR histories from submitted runs, and while I've mostly gotten it to line up with what's on the site in the History tab of the boards, I've noticed something I'm curious about.

In the History tab on the leaderboards (for example, this one), if two WRs happened on the same day, it reports how long the older run stood down to the minute (1 hour, 22 minutes for the records on 2024-04-20 in the above). Runs are only submitted with a date field rather than a timestamp, and in the case of these two runs, the earlier one was actually submitted 4 days later, 2024-04-24, while the latter one was submitted 2024-04-20.

I don't think it's necessarily inaccurate, but I am curious where the numbers are coming from, and if there's any way to get them from the API.

i assume the timestamp comes from either the date submited or date verified as those have datetime instead of just a date.

but yeah wrs on the sameday will be tricky unless you manually get the precise datetime for when the runs were done. you cant even really assume that the slower run of the two wrs on one day was done first. it could be that someone got a lets say a 21 minute time but hadnt submited it yet and the other one got a 22 thinking its a wr as it is faster than the fastest on the leaderboard.

I thought it might be either of those, but this run with a time of 1:49:43.187 was submitted with a timestamp of 2024-04-24 05:06 and verified at 2024-04-30 13:31, while this run with a time of 1:46:32.183 was submitted 2024-04-20 21:22 (4 days earlier) and verified 2024-03-28 09:06 (2 days earlier). Obviously there's a degree of unreliability in all of this (people don't always submit the correct date, after all, so I can't imagine asking them for an exact timestamp), and if I wasn't there for one of the 2000+ WRs posted to the Pizza Tower board I can't fully recreate a timeline, so I mostly was curious what the basis of the reported time a record stood for is.