Hi beehaw friends! Long time no C^1^!
Konform Browser version 140.12.0-100 was recently released and if you aren't aware it's time to upgrade! ^2^
Konform Browser is a free/libre and open-source (FLOSS) fork of Firefox ESR with the primary goals of security, privacy, and user freedom. Shows by example how these three goals don’t have to be at odds but support each other and work in harmony. Runs lean and light with lights off out of the box, while making it convenient to toggle on the features you want. All telemetry removed, none added. Fingerprinting and tracking extras with base defaults on par with (or exceeding) Tor Browser, still keeping common-sense tweaks like dark mode and installation of self-built addons available without making a fuss about it. Graceful degradation for private networks and more granular control for those who want a browser that really conforms.
"ESR" means there's a major upgrade coming up soon with the expected jump from Firefox ESR version 140 to 153 next month. Work has already been ongoing for a while to prepare Konform Browser v153 to be the most secure Firefox build at release. Early alpha builds based on FF153beta are available for anyone who wants to do early testing or help out with any other contribution.
Current Konform Browser 140.x is production-ready and expected to keep receiving security updates and bugfixes for at least a couple of release cycles after initial v153 release so users can upgrade at their leisure.
If you try it, would love to hear your feedback on the browser - and if you like it, tell your friends!
FAQ
Installation instructions provided for most Linux distros
New: Artix Linux package, Gentoo ebuild
Releases
Mastodon: https://techhub.social/@konform
^1^ ~but~ ~not~ ~without~ ~C++~
^2^ ~or~ ~install~ ~😘~
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:
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