

Sounds frustrating and I can see how that can be confusing. Had similar peeves with other imposed limitations that initially drove motivation of developing this project so can relate!
While we have to recognize that there is inherent conflict in expectations of “browser doesn’t disclose my location” and “website knows my timezone” and that Konform Browser will continue defaulting to privacy, you highlight gap in UX and user control that I agree can be improved on. Shouldn’t be too much work to add more make more discoverable selective settings UI for this too in a future release.
There’s some other aspects that often play into this particular scenario and can vary per site:
- Apps showing relative time like “10 hours ago” or “in 15 minutes” should not be affected by any of this.
- Scheduling for events on services like the ones you mention also shouldn’t be affected by this: Time for events is global but display will be affected.
- There are are a lot of bugs in webapps out there that can be interacting with localtime in incorrect ways. It’s complicated1.
Try being a part of a team in multiple timezones, some of which follow Daylight Savings Time (from different dates) and some not. Now schedule a recurring weekly meeting for the same time and coordinate that over chat. This is just inherently messy. Communicating this properly in UI is subtle and confusion like the one you described often arise when webapp developers assumptions and user assumptions don’t align. Some even say we should do away with timezones alltogether.
1: Someone even made list of lists of falsehoods programmers believe about time













deleted by creator