Detecting clock drift

[slifty]

I just spent quite some time trying to figure out why API calls were failing for minutes at a time only to start working again despite no changes on the backend / devenv!

It turns out it was because of server timestamp drift -- the server thought it was the past, so the bearer tokens generated on my machine looked like they were from the future and were being rejected (until time caught up).

It's my understanding that this drift has caused other problems (e.g. queue pileups).

It would be great to fix this issue; I imagine I won't be the last dev who spins wheels for a few hours trying to navigate rifts in the fourth dimension!