> Mozilla/5.0 (Linux, Android 11) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Mobile Safari/537.36

Chrome/91 would be from 2021 [1]. Normal operations from Chrome would be to automatically update so Brave is an outlier here which does not match the goals of the Brave project. If this is an updated version of Brave, please file an issue with Brave as this string should be kept updated.

[1] https://en.wikipedia.org/wiki/History_of_the_web_browser#Web_browsers_by_year

imperva recommends blocking all Chrome user-agents below 100 on page 34 of their 2025 Bad Bot Report [2] and based on the data I am seeing that is sound advice.

[2] https://www.imperva.com/resources/wp-content/uploads/sites/6/reports/2025-Bad-Bot-Report.pdf

Best,
Michael
GPG Key: 4337 2794 C8AD D5CA 8FCF  FA6C D037 59DA B600 E3C0

On 11/29/25 20:13, Bruno Haible via Discussions among Savannah Hackers, open subscription 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?

Bruno

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