[–] 2 points 4 months ago*

Even so, it does not follow that this community should provide that commercialization venue. If you want me involved in solving your business problems or monetization strategy, we should discuss terms and rates first.

  • source
  • parent
  • context
  • [–] 2 points 4 months ago* (last edited 4 months ago) (1 child)

    If you work for a company or own the company you are still making a self- promotional post for a company, and the rule applies.

    So if the exact same post is posted by a friend instead it's suddenly accepted? Why is self-promo meaningfully less desired than third-party-promo if they have similar results?

    You seem to be vastly in the minority.

    Might be! That one's framed as just personal preference and not policy suggestion because I don't think "allow all things I like and ban everything I don't" makes for good governance ;)

    So a more restrictive rule?

    More restrictive in one sense (what content and what's ok to "promote" for) but more allowing in another (you can talk about something even if you are involved or associated).

  • source
  • parent
  • context
  • [–] 2 points 4 months ago* (2 children)

    Thank your for replying, this is encouraging and sounds like moderation of this community is shaping up.

    Whichever side the ruling falls I think that feedback channel would be very good. Just having a way for a submitter to ask from mod(s) why the submission was targeted might be the difference between them turning into a great contributor vs either just leaving or starting to play circumvention games (in especially bad cases turning into antagonistic trolls). Speaking from how I've seen those dynamics play out in other communities.

  • source
  • parent
  • context
  • [–] 3 points 4 months ago* (last edited 4 months ago) (3 children)

    Thank you for thoughtful engagement!

    I think that becomes even more problematic. Why is it better that I shill for a company I'm getting kickbacks from (some VPN providers excel at this game) rather than one I'm responsible for? Besides, this just lead to submarining ("viral marketing" is an entire industry!) and people pretending to "have just stumbled across this project, what do you guys think?" or being "just a happy customer".. And to some extent t becomes a game of social status, where well-connected people can just ask their friends to post on their behalf.

    Judge the message and topic, not the messenger (as long as they are human acting in good faith and not "written with help by AI", obv).

    Besides of those issues, my personal preference would be to keep the focus on self-hosting. So talk of hardware or shipped software might be on-topic but not service providers. There are plenty of places to discuss cloud-hosting, VPNs, which PaaS is best, or whatnot.

    And I would actually be much more interested in seeing a post from a founder talking about things their company is doing relevant to self-hosters, vs yet another post of "which provider is best right now and what do you use?" or "Company X currently has a sale/launched product Y".

    While it might filter out some good stuff, I would be all for a ban of any promotion of commercial or proprietary products and services alltogether but allow for self-hostable and in particular FLOSS stuff (where I guess some carve-out or clever formulation could be made to allow for commercial but self-hostable software - either stance on that one seems fine to me).

  • source
  • parent
  • context
  • [–] 9 points 4 months ago* (last edited 4 months ago) (4 children)

    I would like some clarity on general apparent self-promotion of open source projects as well. As in, points 1-4 don't apply and 5 depends on your definition of "advertisement".

    I'm bringing this up because I (once) previously attempted to share a project^1^ I maintain on here. I did take some effort to include some context and discussion points for selfhosters in order to make it more tailored and stay safe on Rule 3. It was quickly removed by mod. I tried reaching out to one of the mods to try to understand what was wrong. They were friendly and said they weren't involved and would forward to the relevant people and since then I haven't heard back. It would be very helpful to be able to get some feedback on why submission was removed so we can learn how future submission attempt could be improved (or abandoned).

    ^1^: FLOSS, no commercial or otherwise proprietary parts or relations, no slop or clank in the process

  • source
  • parent
  • context
  • [–] [S] 3 points 4 months ago*

    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^1^.

    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

  • source
  • parent
  • context
  • [–] [S] 2 points 4 months ago* (last edited 4 months ago)

    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)

  • source
  • parent
  • context
  • [–] [S] 2 points 4 months ago* (2 children)

    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?

  • source
  • parent
  • context
  • [–] [S] 3 points 4 months ago (2 children)

    Thanks! Would be great to hear your thoughts and experience after trying it out, if you do! BTW, I keep fishing for feedback not just because I like hearing user stories but also since with no telemetry (or a qa team; lol), user reports become that much more valuable in development, catching issues and better understanding the UX ^^

  • source
  • parent
  • context
  • [–] [S] 3 points 4 months ago* (last edited 4 months ago) (2 children)

    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?

  • source
  • parent
  • context
  •  

    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 😘

    [–] 4 points 4 months ago* (last edited 4 months ago) (1 child)

    "Facebook Container" seems redundant if you already use Multi-Account Containers and set it up accordingly, yes. Other than that it doesn't sound over-the top at all and a reasonable configuration.

    Doesn’t Strict mode block third-party cookies anyway?

    Almost, but not entirely. For that you need First-party Isolation (privacy.firstparty.isolate pref: https://bugzilla.mozilla.org/show_bug.cgi?id=1330467),

    containerises first-party cookies too, but I wouldn’t need that.

    It does do that - if it didn't, there wouldn't be any "multi-account" to it.

    With a profile like that you might also find Konform Browser relevant to your interests with more private defaults and convenient toggling of modes and features. https://konform-browser.codeberg.page/

    It comes with a debloated version of Multi-Account Containers, which can also be installed as a normal addon into other Firefox builds: https://codeberg.org/konsortium/multi-account-containers-lite

  • source
  •  

    It's been a while!

    Konform Browser version 140.12.0-100 was recently released and if you aren't aware it's time to upgrade! ^1^

    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^ or install 😘

    Konform Browser - Hardened Firefox ESR fork (konform-browser.codeberg.page)
     

    Konform Browser is a web browser with the goal of promoting user freedom and access to the rights of security, privacy and anonymity. It is intended as a general-purpose browser fit both for daily online browsing as well as targeted deployments in secure or untrusted environments. Has stronger security with hardened defaults, better privacy and fingerprint protection while keeping user in control.

    About^1^

    Source

    Release notes^1^

    AI/LLM policies: 1 2

    ^1^: See here for answer to "Differences to Librewolf?"

    Konform Browser - Hardened Firefox ESR fork (konform-browser.codeberg.page)
     

    Konform Browser is a web browser with the goal of promoting user freedom and access to the rights of security, privacy and anonymity. It is intended as a general-purpose browser fit both for daily online browsing as well as targeted deployments in secure or untrusted environments. Has stronger security with hardened defaults, better privacy and fingerprint protection while keeping user in control.

    About

    Source

    Release notes

     

    Would like to share this FLOSS project been working on for a while now and hope that is cool with you all!

    Was not satisfied with status quo on browser options for our use-cases and needs - hence Konform Browser evolved.

    Whether accessing private resources and actually wanting to keep that private, or minimizing traces left when surfing online, Konform Browser makes that easier with uncompromising hardened defaults combined with extended configuration UI and features like built-in container tabs for additional isolation and more flexible proxy configuration.

    Binaries only provided for Linux but sources should be buildable for other platforms.

    Looking forward to hear thoughts and feedback on project!

    Source

    Readme

    Releases

    Mastodon: https://techhub.social/@konform

     

    Keeping up with security updates for your web browser is of increasing practical relevance. Under normal conditions this means important updates roughly every couple of weeks.

    Mainline firefox or chromium packages are typically easy mode: For most people it's a matter of staying on top of regular pacman updates. torbrowser-launcher updates from inside the browser and is also usually painless to manage.

    Running custom builds or forks from AUR requires more attention. Is the AUR package up to date? If it's a fork: Are security updates from Mozilla/Google downstreamed in a timely manner? Have you built it? Can you still build it? How long since you pulled and rebuilt that ungoogled-chromium binary and how many CVEs has it racked up by now?

    Anyone running firefox-esr or any derivative like icecat, waterfox^1^, mullvad-browser or konform-browser from AUR should probably be paying attention to this right now:

    Arch Linux repositories updated llvm and clang to v22 on 2026-03-07. This caused a regression for Firefox ESR packaging resulting in compilation failure when building.

    Firefox ESR 14.9.0 was released on 2026-03-24.

    This means that since then, users of the AUR packages for these browsers have not been able to build a new version with security fixes on up to date Arch Linux system. Some users may be prepared to handle this by maintaining separate build infra with internal registry where keeping system packages frozen on older version is acceptable but for everyone else, this is a conundrum.

    Anyone browsing the web on firefox-esr or a derivative should make sure you get fixes for the issues addressed in 140.9.0 asap.

    konform-browser AUR package has been patched with clang 22 toolchain fixes from mozilla and should now build succesfully. The other forks including firefox-esr will still need manual patching or downgrading clang toolchain packages to v21 to compile. The konform-browser patches for clang 22 are in the AUR repo and should be portable to the other browsers too. If others can share their results in testing (both X11 and Wayland) or reviewing the fix, this might help in sorting out the firefox-esr situation sooner than later, too.

    ^1^: Looking at git log it claims to build as of the wasi-compiler-rt21 makedepends but I have still not been able to make it compile when attempting. Please LMK if I'm holding it wrong and there is a way!

    Announcement brought to you by Konform Browser

     

    Keeping up with security updates for your web browser is of increasing practical relevance. Under normal conditions this means important updates roughly every couple of weeks.

    Mainline firefox or chromium packages are typically easy mode: For most people it's a matter of staying on top of regular pacman updates. torbrowser-launcher updates from inside the browser and is also usually painless to manage.

    Running custom builds or forks from AUR requires more attention. Is the AUR package up to date? If it's a fork: Are security updates from Mozilla/Google downstreamed in a timely manner? Have you built it? Can you still build it? How long since you pulled and rebuilt that ungoogled-chromium binary and how many CVEs has it racked up by now?

    Anyone running firefox-esr or any derivative like icecat, waterfox^1^, mullvad-browser or konform-browser from AUR should probably be paying attention to this right now:

    Arch Linux repositories updated llvm and clang to v22 on 2026-03-07. This caused a regression for Firefox ESR packaging resulting in compilation failure when building.

    Firefox ESR 14.9.0 was released on 2026-03-24.

    This means that since then, users of the AUR packages for these browsers have not been able to build a new version with security fixes on up to date Arch Linux system. Some users may be prepared to handle this by maintaining separate build infra with internal registry where keeping system packages frozen on older version is acceptable but for everyone else, this is a conundrum.

    Anyone browsing the web on firefox-esr or a derivative should make sure you get fixes for the issues addressed in 140.9.0 asap.

    konform-browser AUR package has been patched with clang 22 toolchain fixes from mozilla and should now build succesfully. The other forks including firefox-esr will still need manual patching or downgrading clang toolchain packages to v21 to compile. The konform-browser patches for clang 22 are in the AUR repo and should be portable to the other browsers too. If others can share their results in testing (both X11 and Wayland) or reviewing the fix, this might help in sorting out the firefox-esr situation sooner than later, too.

    ^1^: Looking at git log it claims to build as of the wasi-compiler-rt21 makedepends but I have still not been able to make it compile when attempting. Please LMK if I'm holding it wrong and there is a way!

    Announcement brought to you by Konform Browser

     

    I would like to invite all of you Linux users to check out the latest release of Konform Browser.

    Konform Browser is a free/libre and open-source (FLOSS) fork of Firefox with the primary goals of security, privacy, and user freedom. Hoping to be an example of how these three goals don’t have to be at odds but support each other and work in harmony. Would love to hear your feedback on if it's in the right direction and what can be improved.

    Been posting on and off the lemmies about the project during 2026 and previously on this community. Below are major highlights since 140.8.0-103 update from two weeks back:

    • Bundling and enforcing use of bundled fonts. Konform Browser now carries the same font-loading patches and bundled fonts as Tor Browser and Mullvad Browser. While this does increase download- and installation sizes, it has two clear benefits: - Significantly improved resistance against font fingerprinting used by tracking scripts. Konform Browser should now be more robust against this attack by having shared global font fingerprint. - All languages and scripts should render as expected regardless of what fonts you have installed on system.
    • Also bundled is now Multi-Account Containers Lite addon. It's a debloated^1^ fork of Firefox Multi-Account Containers so you can utilize Container Tabs and set per-container proxies without installing addon for it.
    • While "AI chatbot" feature was already disabled and hidden by default, it was previously still possible to trigger activation of proprietary networked centralized cloudbots by setting pref browser.ml.chat.enabled=true. These have now been fully removed and replaced by a single provider utilizing locally running llamafile instance.
    • Ported a bunch of security fixes and improvement on fingerprinting protection from FF Rapid Release and Tor Browser which didn't make it into upstream FF ESR.

    For details and references see linked release notes. For even more details I hope the commit log is digestible.

    Packages available for most Linux distributions.

    AUR source package

    Releases

    README

    Konform Browser is also on Mastodon where followers make me happy: https://techhub.social/@konform

    ^1^: Similarly as rest of Konform Browser: Removal and disabling of telemetry, analytics, ads, touting, nags ("call-to-actions"), and integrations with centralized proprietary service (Mozilla VPN in this case).

     

    I would like to invite all of you Linux users to check out the latest release of Konform Browser.

    Konform Browser is a free/libre and open-source (FLOSS) fork of Firefox with the primary goals of security, privacy, and user freedom. Hoping to be an example of how these three goals don’t have to be at odds but support each other and work in harmony. Would love to hear your feedback on if it's in the right direction and what can be improved.

    Been posting on and off the lemmies about the project during 2026. Below are major highlights since 140.8.0-103 update from a week and a half back:

    • Bundling and enforcing use of bundled fonts. Konform Browser now carries the same font-loading patches and bundled fonts as Tor Browser and Mullvad Browser. While this does increase download- and installation sizes, it has two clear benefits:
      • Significantly improved resistance against font fingerprinting used by tracking scripts. Konform Browser should now be more robust against this attack by having shared global font fingerprint.
      • All languages and scripts should render as expected regardless of what fonts you have installed on system.
    • Also bundled is now Multi-Account Containers Lite addon. It's a debloated^1^ fork of Firefox Multi-Account Containers so you can utilize Container Tabs and set per-container proxies without installing addon for it.
    • While "AI chatbot" feature was already disabled and hidden by default, it was previously still possible to trigger activation of proprietary networked centralized cloudbots by setting pref browser.ml.chat.enabled=true. These have now been fully removed and replaced by a single provider utilizing locally running llamafile instance.
    • Ported a bunch of security fixes and improvement on fingerprinting protection from FF Rapid Release and Tor Browser which didn't make it into upstream FF ESR.

    For details and references see linked release notes. For even more details I hope the commit log is digestible.

    Packages available for most Linux distributions.

    AUR source package

    Releases

    Konform Browser is also on Mastodon where followers make me happy: https://techhub.social/@konform

    ^1^: Similarly as rest of Konform Browser: Removal and disabling of telemetry, analytics, ads, touting, nags ("call-to-actions"), and integrations with centralized proprietary service (Mozilla VPN in this case).


    Cross-post. Original Thread @ https://discuss.tchncs.de/post/56107349

     

    I would like to invite all of you Linux users^1^ to check out the latest release of Konform Browser.

    Konform Browser is a free/libre and open-source (FLOSS) fork of Firefox with the primary goals of security, privacy, and user freedom. Hoping to be an example of how these three goals don’t have to be at odds but support each other and work in harmony. Would love to hear your feedback on if it's in the right direction and what can be improved.

    Been posting on and off the lemmies about the project during 2026. Below are major highlights since 140.8.0-103 update from a week and a half back:

    • Bundling and enforcing use of bundled fonts. Konform Browser now carries the same font-loading patches and bundled fonts as Tor Browser and Mullvad Browser. While this does increase download- and installation sizes, it has two clear benefits:
      • Significantly improved resistance against font fingerprinting used by tracking scripts. Konform Browser should now be more robust against this attack by having shared global font fingerprint.
      • All languages and scripts should render as expected regardless of what fonts you have installed on system.
    • Also bundled is now Multi-Account Containers Lite addon. It's a debloated^2^ fork of Firefox Multi-Account Containers so you can utilize Container Tabs and set per-container proxies without installing addon for it.
    • While "AI chatbot" feature was already disabled and hidden by default, it was previously still possible to trigger activation of proprietary networked centralized cloudbots by setting pref browser.ml.chat.enabled=true. These have now been fully removed and replaced by a single provider utilizing locally running llamafile instance.
    • Ported a bunch of security fixes and improvement on fingerprinting protection from FF Rapid Release and Tor Browser which didn't make it into upstream FF ESR.

    For details and references see linked release notes. For even more details I hope the commit log is digestible.

    Packages available for most Linux distributions.

    AUR source package

    Releases

    Konform Browser is also on Mastodon where followers make me happy: https://techhub.social/@konform

    ^1^: Non-Linux users: This is the year to convert! (Or help out with porting if you're a rare BSDer ;))

    ^2^: Similarly as rest of Konform Browser: Removal and disabling of telemetry, analytics, ads, touting, nags ("call-to-actions"), and integrations with centralized proprietary service (Mozilla VPN in this case).

     

    Good $TIME_OF_DAY, beehaw folks!

    Today I come to share the first announcement of Konform Browser 140.8.0-103 and what's new since previous update post last week!

    If you are new to Konform Browser, it was previously introduced to the lemmies in this post. In one sentence, it's a web browser for Linux based on Firefox ESR with the primary goals of security, privacy, and user freedom. Hoping to be an example of how these three goals don't have to be at odds but support each other and work in harmony.

    Without more ado, some highlights of the new since last week:

    • Exposed UI for "Local AI" features like full-page translations, link previews and configuring local models. These features are all disabled by default but now easier to selectively enable and keeps working locally and offline more gracefully when remote updates are disabled.
      • This coincides funnily with the new "AI killswitch" news from FF v148 this week. Konform Browser approaches the "AI/ML" feature-set from the opposite end from upstream: Selective opt-in, progressive enhancement, and graceful degradation, while making sure any external endpoints or keys are user-configurable.
      • Check out about:translations (which is pretty handy and reliable) and about:inference (where you can now load and test arbitrary models from HuggingFace)!
      • The "Link Preview" feature is rather janky and considered experimental.
      • The "AI chatbot" integration to bigcloudtech is unaffected by these changes and remains disabled under every preset.
    • Latest security fixes up to Mozilla Firefox ESR 140.8.0.
    • Various privacy improvements
      • navigator.sendBeacon() now disabled by default (re-enabled by "Just Make It Work" preset)
      • Ported over several relevant patches from Tor Browser
      • Proxy bypass protection enabled to reduce risk of network leaks
    • Changes made on about:welcome now take effect immediately without requiring browser restart
    • UI: Disabled various nags and onboarding callouts (no more "Hey please try the new feature" in the middle of your workflow)

    For more details check out release notes and (if that's not detailed enough for you :p) commit log.

    If you check it out, would love your feedback on the project in general and, if this isn't a first, your take on development and recent updates. Fellow devs: Doors wide-open for new (carbon-based) contributors ^^

    Konform Browser is now also on Mastodon: https://techhub.social/@konform

    Packages available for most Linux distributions.

    AUR source package

    Releases

    view more: next ›