This might be a UTC vs local timezone thing. I will look into it.

I hope to come back to this. If anyone else wants to, then can fix this.

Pretty sure it is a UTC vs local timezone issue. We use UTC on the backend to generate these buckets.

The issue is that the SQL query truncates the dates in UTC. So only UTC date buckets work.

The counting calculation is cached.

See the counting here:

A possible solution is to expose the raw timestamps as utc values, and have the golang make the correct date buckets. We can then do the calculation 24 times, one for each major timezone. To accommodate weird timezones, we just do timezone offsets, and let the caller choose the closest offset to them.

Thoughts?

Just realized the postgres does a group by on the UTC date to remove duplicates. So we cannot return the raw date from the sql, or else we could be returning a large amount of rows.

Hmm 🤔

My PR describes what I implemented. This makes the response able to change in reference to the caller's local timezone.

I'm going to reopen this until we change the frontend to show the proper values based on the user's timezone. There is a backend fix, but it's not really obvious/accessible for the user.