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 complicated¹.

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.

¹: Someone even made list of lists of falsehoods programmers believe about time

deleted by creator

If you’re talking about Librewolf’s “resist fingerprinting”:

To set the record straight, ResistFingerprinting was originally developed by Tor Browser developers, and is for some time now part Firefox (and therefore all forks) behind the privacy.resistFingerprinting (“RFP”) preference. So credit there goes to those devs, Tor Projectt, ad Mozilla. Konform Browser and Tor Browser have this on by default. There is also the related more recent and complex privacy.fingerprintingProtection (“FPP”) system. LibreWolf has historically been on RFP too - I’m not up to date if that’s still the case or if they’ve migrated over to FPP yet as I understand that is the intention of maintainers. The difference between the two is more than I bear to explain here and a bit of a rabbit hole x)

Hm, could you be more specific exactly what your issue is, and what behavior you are expecting? It sounds like you could be referring to this: https://bugzilla.mozilla.org/show_bug.cgi?id=1364261

There is a workaround mentioned at the bottom of that thread which should have the same result on all three browsers (and sounds like what you want, except having to disable ResistFingerprinting?). Just like for the forced-light-theme, I think it can make sense to provide a more convenient and obvious way to change the timezone without having to impact the other privacy protections. Might take a look at that but most likely after ESR153.0 is out of the way. If I read you right: Do you expect to be able to toggle this per-site, or would you be satisfies with a global toggle similar to the one we already have for allowing dynamic themes under RFP?

I am an exclusive flatpak user (as much as possible at least)

In that case I will certainly encourage you to get more comfortable with the flatpackaging side and getting that local build env up for yourself! Having self-hosted repo for self-built packages¹ in whatever format you use is one of the most liberating things one can set up IMO. Looking forward to seeing you around on the issue tracker ;)

¹: Ideally with sensible lifecycle 🤭

Not highly prioritized since:

1. We’d need someone with a Github account (ie not us) to step up as maintainer for that in order to be on flathub.
2. Arguably problematic security tradeoffs for browser (yes flatpak has its own sandboxing but that disables the one of browser)
3. Users run into frustrating and confusing edge-cases with not working devices, directories, addon integrations, etc, and not grokking the security model. Flatseal is a bit obscure still.
4. Container option exists for advanced users who want containerization

That said, there is a starting point - if anyone feels inclined to pick it up shows up on the forge, would be happy to collaborate towards that. You can also just go ahead and package it up independently from us if you wish (free software and all that).

Are you on some dist existing package repos aren’t covering? Or just a matter of preference?