I was very pleased this morning to see that it’s my cakeday (on the forum I administer):
And out of curiosity I went to see who else’s cakeday was nearby. Strangely, though, the anniversaries page seems to be a day in the past:
Could it be because I’m in GMT+8?
That’s what I think.
Given that Discourse localizes the times it shows you everywhere else in the UI, I feel this is still a “bug” and should be fixed.
So there are 24+ different cake day sets? That seems crazy.
That’s one way to look at it I guess. But I’m assuming the users are queried on page load, so there’s really only “one” set at a time.
Here’s a better example. The post you just made shows up for me as “June 8, 2017 12:45 AM”. If I was to fly across the country to California, I’d expect that post to show as “June 7, 2017 9:45 PM”.
…and I just earned the “anniversary” badge this morning. This does feel like a bug to me.
Could it be mitigated by simply changing the timezone of the server to something more applicable for my community? We’re (mainly) in Australia, so processing everything as, say, GMT+8 or GMT+10 would make this all feel less odd.
Not a major issue, of course. 
Since the server doesn’t know a user’s time zone, maybe the easiest fix for this would be to award the badge one day later? For some, that will mean they get it late, but that will probably not be experienced as a bug as much as an early award is.
Another option might be to simply specify in the UI that these times are based on the server’s time zone.
Ich denke, dass du im Kontext einer stark lokalisierten Community die Möglichkeit haben solltest, die Zeitzone für den Discourse Cakeday anzugeben. Die Serverzeitzone zu ändern, ist jedoch nicht wirklich etwas, das wir tun können.
Das ist eine heikle Angelegenheit, und ich bin mir nicht sicher, wie man sie lösen soll, selbst jetzt, wo wir es den Benutzern ermöglichen, „Zeitzonen
Ich glaube, @tgxworld hat das bereits behoben, um den Zeitzonenoffset zu berücksichtigen, über:
und
EDIT: Ich befinde mich in der Zeitzone UTC+5:30, habe aber einen Offset von 6 Stunden, sodass ich einige Randfälle für Benutzer sehe, die zwischen 23:30 und 00:00 Uhr ein Konto erstellt haben. Ich untersuche das.
Behoben durch:
