Over the last few days, I have been implementing the new custom timezone feature to allow anyone to publish in their own 24-hour cycle.
Before that, the countdown was based on Zurich’s time where the server is located. 200WaD is now a global website with people from all around the world, so it’s now making sense to add a timezone support.
Adding a timezone information to each user is not hard. What is hard is transitioning from a single timezone architecture to a truly global website without breaking anything.
Of course, I shipped fast but broke the website several times over the last few days. Sorry if you have been affected, but this is for the greater good :P
The main problem I faced is how to keep the day streaks intact after changing the timezone. To do that I added a timezone field to the posts and comments as well. There still might be some problem to readjust: if the user doesn’t post before midnight the day it changed the timezone setting, the day streak will be broken. If this happens to you, please wave at me and I will fix your post’s dates to keep your streak going.
One common thing people tell you when you start a product is to do things that don’t scale. Well, I will never do this same mistake again: for glocal websites, internationalization should be planned from the get-go.
This post is published to ensure the timezone change has been correctly made. Let’s hope I don’t break anything else 🤞