Had a couple of user reports regarding the Devotee badge, that requires 365 days of consecutive logins to gain. The issue seems to be that people on timezones far away from UTC (say, PST +8) have to take that into account that the underlying ‘day’ is in UTC times. We are seeing European users getting the badge, while others not understanding why they are not.
What I think has happened is that someone on say PST +8 will login early morning on March 14th, then late night on March 15th (to them a login each day) but the system badge query will see March 15th as entirely ‘skipped’, breaking their 365 consecutive days run. This can be upsetting for the end user, especially if they are close to the end of their year ‘run’.
I know that timezones and database queries often don’t mix well, but I’d ask if anything could be done to ‘widen’ the query, perhaps to give tolerance for a ‘UTC day’ when it’s longer badge periods like a year - thanks.