On 11/29/25 19:13, Bruno Haible wrote:
Jacob Bachmeyer wrote:
I was explaining why the Falkon (and presumably
also Brave) developers did not make their browsers distinguishable from
Chrome.
Well, lists.gnu.org and savannah.gnu.org *do* distinguish Brave and Chrome.
This is precisely what I'm complaining about.

I'm guessing that this distinction is based on the User-Agent string.
But maybe it is actually something else in the HTTP request?

As Michael McMahon described in his reply, the servers think that Brave is an archaic Chrome version.  Chrome auto-updates, so such an archaic version should no longer be in use.

The "fun part" with Qt5 Falkon is that it claims to be Chromiuim 87.0.4280.144 even though it *actually* has security fixes backported current to 135.0.7049.95.  (I know that is old, too; I finally have the last piece of hardware needed before I can migrate to a distribution that actually updates.)  (ARM laptops do not have the most thorough of support.)

QtWebEngine generally identifies as the Chromium version that was initially imported and cleaned up to produce it, even after security fixes have been backported.  The Qt Wiki has details at <URL:https://wiki.qt.io/QtWebEngine/ChromiumVersions>.  This affects Falkon, but I think Brave is an entirely separate Chromium fork.


-- Jacob


  • [Savannah-hackers-pu... Discussions among Savannah Hackers, open subscription
    • Re: [Savannah-h... Jacob Bachmeyer
      • Re: [Savann... Discussions among Savannah Hackers, open subscription
        • Re: [Sa... Jacob Bachmeyer
          • Re:... Discussions among Savannah Hackers, open subscription
            • ... Michael McMahon
              • ... Collin Funk
              • ... Discussions among Savannah Hackers, open subscription
                • ... Michael McMahon
                • ... Discussions among Savannah Hackers, open subscription
            • ... Jacob Bachmeyer
              • ... Michael McMahon

Reply via email to