From the article:

"I know for a fact that Wikipedia operates under a CC BY-SA 4.0 license, which explicitly states that if you’re going to use the data, you must give attribution. As far as search engines go, they can get away with it because linking back to a Wikipedia article on the same page as the search results is considered attribution.

But in the case of Brave, not only are they disregarding the license - they’re also charging money for the data and then giving third parties “rights” to that data."

  • jacktherippah@lemmy.worldEnglish
    5·
    1 year ago
    • On Android, Firefox lacks per-site process isolation, which makes it less secure than Chromium browsers (not insecure, just less secure.)
    • With privacy.resistFingerprinting on, Firefox on Android is stuck at 60hz, which I don’t like.
    • There is a noticeable difference in performance between Firefox and Chromium. Firefox is consistently slower when loading webpages, which you notice after using Chromium.

    Don’t get me wrong, I like Firefox. I use LibreWolf on desktop. I just can’t justify using it on Android, at least not yet. Guess I’ll go back to using Vanadium.

    • xthexder@l.sw0.comEnglish
      3·
      1 year ago

      When I switched from Chrome to Firefox Mobile I didn’t notice any slowdown. I’m surprised you noticed anything because presumably your phone is newer than mine, since I’ve only got a 60Hz display in the first place.

      • glacier@lemmy.blahaj.zoneEnglish
        1·
        1 year ago

        It is a setting in the about:config menu on FireFox Beta and Nightly. When enabled, the browser tries to hide certain information about your browser and device from websites.

      • jacktherippah@lemmy.worldEnglish
        1·
        1 year ago

        This might not matter to 60hz users but to the ones used to 120hz, it is jarring to go back to 60hz. Everything feels a split second slower and animations look pretty choppy.