The new system with automatic timezone adaptation is great, but there's 1 catch: It's not working right when you're offline. What I mean by that is that it automatically places you in UTC when you're not logged in. I think most people are not in UTC, but are instead UTC+1 (as long as winter lasts anyway, after that it's a different story entirely). If you keep the website open for a longer amount of time, you'll get logged out automatically. At that point that becomes a problem. There is of course a debate to be had about how people use the website, but in my opinion the best way is to keep it open and refresh it every once in a while. Having to log in every time is a hassle, and besides, you can see everything without logging in. You can't comment and sign up, of course, but you don't need to very often.
What I suggest, if it's possible without too much effort, is to take the user's IP address, see where that is located, and decide the timezone from there. It should mostly do the job, until they log in and set it for themselves.
It's not necessary to put a lot of effort into that, because, well, there's the little (UTC) timezone marker after each time on events. Still, I think it would help the usability of the website.
The new system with automatic timezone adaptation is great, but there's 1 catch: It's not working right when you're offline. What I mean by that is that it automatically places you in UTC when you're not logged in. I think most people are not in UTC, but are instead UTC+1 (as long as winter lasts anyway, after that it's a different story entirely). If you keep the website open for a longer amount of time, you'll get logged out automatically. At that point that becomes a problem. There is of course a debate to be had about how people use the website, but in my opinion the best way is to keep it open and refresh it every once in a while. Having to log in every time is a hassle, and besides, you can see everything without logging in. You can't comment and sign up, of course, but you don't need to very often.
What I suggest, if it's possible without too much effort, is to take the user's IP address, see where that is located, and decide the timezone from there. It should mostly do the job, until they log in and set it for themselves.
It's not necessary to put a lot of effort into that, because, well, there's the little (UTC) timezone marker after each time on events. Still, I think it would help the usability of the website.