Track server date via headers to avoid drifting. #119
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With the new-ish time-gate on after, a user who doesn't get many chats but continues to request after:date of last chat will eventually get locked out of new chats.
Previously, this used local dates to try to avoid that, but local dates need not correlate at all to server dates. This patch uses server dates from the date header where possible, falling back to local dates only if necessary.
This should make it more reliably avoid drifting and getting stuck without chats forever.