I do. Perhaps a slightly more zoomed out screenshot might illustrate (by the way all this comes from this calendar):
So in one view I have events at:
- 14:00 on May 2nd - and that’s in BST which is my timezone, so it’s correct
- 10:30 on May 11th - but in Amsterdam, so actually 9:30 in my timezone
- 14:00 on May 17th - again, in my timezone so it’s right
- 10:00 on May 25th - but in US East, so actually 15:00 my time
In other words, the view is misleading. When I see a calendar, I would expect everything to be shown in one timezone - that’s what you get from the webcal / ICS links, after all. Things get more fun if I move the 10:00 GMT-5 to the 17th:
So clearly this is just a display thing, since the calendar knows 10:00 -5 is later than 14:00 +1. When you have a busy calendar, it becomes obvious that timezones are in play, but when there’s only one event on a given day I think it’s a natural assumption that it’s in your zone.
I read though your link, and for the most part it does makes sense - especially for the agenda view where there’s more room. Here I’d suggest either showing the timezone (possibly not enough space though), using local-dates (I think I saw that on your to-do?) or converting the time text to the browser timezone just for the calendar entry.
Some history: Until we set up the events plugin our calendar was on our website (now discontinued in favour of Discourse, but the code is here, it’s a Jekyll site using the iCalendar gem), and there we did convert all events to the browser timezone. My users seem reluctant to add webcal / ICS stuff to their own calendars, so I assume they’ll come to Discourse to see when events are - and then complain at me when they miss stuff.
Sure, it’s from the above linked calendar - webcal link. Here’s a shot of what Google did with it:
Note how the timezone field is not editable, so while the URL is correct (timezone=Europe/London), the choice of UTC by Google is … odd, and annoying