Konform Browser and other bits and bobs.

  • 19 Posts
  • 93 Comments
Joined 8 months ago
cake
Cake day: January 18th, 2026

help-circle

  • 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



  • 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)




  • But can it fool creepjs?

    What does that mean for you, exactly? I know that there is a lot of different ideas out there on how to interpret these results and what “good” means so would be helpful to know what your expectations are to give meaningful answer to such question.

    Anyway, I just tried running the test at creepjs.org and this is result: Test hangs at “57/58: Currently collecting: Private Click Measurement complete”, with no errors in the js console.

    Having compared results with some other fingerprinting suites previously, default settings should give plausible fingerprint corresponding to user base of existing browser. Only Cloudflare seems to hate it: Turnstile on sites in strict mode currently often throw a redirect loop when their troubleshooting tool says all is fine. Is that because fingerprinting protection “works to good” or is broken? You tell me!

    I would appreciate an outside and less biased review, comparison or benchmark on stuff like this! Want to try and report back?






  • There is some talk about this on the readme (“About”) page with more detail on differences in the release notes.

    On “AI”, tooted about this here. As one example, the “AI chatbot” feature is disabled and hidden by default. If user still chooses to enable it via preferences, stock configuration only has one available provider: localhost where user runs their own app (for example llamafile.ai) locally outside of the browser while proprietary integrations1 and telemetry are removed even when feature enabled. I think for all of the AI-features, both the default-disabling and making them work better (or at all) without remote cloud goes deeper in Konform Browser than others like Librewolf.

    Another example is about:translations, which when enabled2 actually works properly when offline after translation models have been downloaded; they are not bundled with browser.

    Let me know if any more questions after reading that!

    1: Like ChatGPT and others

    2: “Basic Functionality” and “Just Make It Work” presets enable local translations feature and downloading of translation models.