• whileloop@lemmy.world
      link
      fedilink
      English
      arrow-up
      119
      arrow-down
      1
      ·
      1 year ago

      If I understand correctly, there’s nothing about Firefox that makes ad blockers any harder to detect. What can Firefox and uBlock do to stop Google from blocking adblock users on the site?

      • AProfessional@lemmy.world
        link
        fedilink
        English
        arrow-up
        104
        arrow-down
        1
        ·
        1 year ago

        They don’t care about Firefox. Chrome is the browser market, they have weakened extensions, they implemented DRM, and here we are.

        • Fester@lemm.ee
          link
          fedilink
          English
          arrow-up
          134
          ·
          1 year ago

          Coming to you later… “Your browser violates YouTube’s Terms of Service.”

            • Sami@lemmy.zip
              link
              fedilink
              English
              arrow-up
              62
              ·
              edit-2
              1 year ago

              They can just phrase it a little differently and argue semantics in front of a bunch of 70 year olds who don’t know what a browser is in a hearing or two. Maybe a couple campaign contributions through completely legal channels and that’s that. Anti trust enforcement has been falling in the US for decades.

              • bobs_monkey@lemm.ee
                link
                fedilink
                English
                arrow-up
                9
                arrow-down
                1
                ·
                1 year ago

                I am cautiously optimistic of that new gal heading the FTC, she’s preparing suits I to Amazon and Google, so we’ll see how that goes

          • callyral@kbin.social
            link
            fedilink
            arrow-up
            13
            ·
            1 year ago

            You could use an extension that changes your user agent but I’m not sure how well that’d work

          • DrQuint@lemm.ee
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            1 year ago

            They’re TRYING, but for now, it would be a user agent extension matter.

      • AphoticDev@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        70
        arrow-down
        9
        ·
        1 year ago

        It doesn’t matter if YouTube can detect uBlock. The great thing about uBlock is you can just block the anti-adblock script. Since Javascript is executed on the user’s computer, it’s trivial to just tell your computer to ignore it. And moving it to server side would cost them too much money in processing power.

        That’s why they want everyone to adopt their DRM, so they don’t have to worry about it.

        • PeachMan@lemmy.one
          link
          fedilink
          English
          arrow-up
          45
          arrow-down
          5
          ·
          1 year ago

          This logic is so flawed lol. It’s also completely trivial for them to detect when their anti-adblock script has been blocked. If it gets blocked, then they can just stop serving you videos.

          There are websites that already do this; it’s not theoretical. The website just doesn’t work if it detects an adblocker.

          • Zikeji@programming.dev
            link
            fedilink
            English
            arrow-up
            24
            arrow-down
            1
            ·
            1 year ago

            Whether or not it’s trivial to detect depends on the method used to block it. It already is an arms race, and said race will continue.

            • Draconic NEO@lemmy.world
              link
              fedilink
              English
              arrow-up
              7
              ·
              1 year ago

              Didn’t Spotify do this a while back, they made threats of account bans as well. In the end it was bypassed and you can still use Adblock in the browser or adfree clients on desktop (or just block ads across device with Adguard or Portmaster), though honestly Spotify kind of sucks in my opinion (usually doesn’t have the music I want and has UI unresponsiveness).

          • AphoticDev@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            1
            arrow-down
            1
            ·
            1 year ago

            OK, show us an example. I’ve never run across a website that adblockers just didn’t work on, but maybe you know of one. Give us an example, and we’ll see if we can bypass that. Then we’ll know which of us understands how Javascript works, and which doesn’t.

      • Goodie@lemmy.world
        link
        fedilink
        English
        arrow-up
        23
        arrow-down
        2
        ·
        1 year ago

        Firefox currently enjoys protection from being “relatively niche” in the browser market (aka not Chromium based trash).

        But if I had to place a bet on which browser would put effort in to protecting your privacy, including which extensions are installed, my bet would be on Firefox over Chrome.

      • ares35@kbin.social
        link
        fedilink
        arrow-up
        19
        ·
        1 year ago

        i think it’s mainly the list maintainers staying on-the-ball with changes to sites. they can move quicker than a giant corporation can develop, test, and roll-out potentially site-breaking changes that could adversely affect ‘billions’ of users.

      • Name is Optional@lemmy.world
        link
        fedilink
        English
        arrow-up
        9
        ·
        1 year ago

        It has always been my understanding that uBlock and uBlock Origin were two totally different extensions for ad blocking. Is this not correct? Back several year ago when ad blockers were new, I recall seeing two different Firefox listings for them, and people would caution users to get uBlock Origin and not the other truncated named one

      • Fades@lemmy.world
        link
        fedilink
        English
        arrow-up
        9
        arrow-down
        2
        ·
        1 year ago

        The difference is Firefox is not a chromium based browser and thus not subject to googles fucking bullshit, esp when we come to things like web drm

      • igorlogius@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        What can Firefox and uBlock do to stop Google from blocking adblock users on the site

        Not sure if you question is serious … but just in case, Mozilla is one of the few non-profit orgs that is fighting for an open web

        ref. https://www.mozilla.org/en-US/about/manifesto/

        and uBlock Origin can literally work its magic because firefox provides the necessary APIs that allows it to work. (old ref. but AFAIK still relevant: https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-best-on-Firefox)

      • UristMcHolland@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        I would love to see YouTube try to block Firefox users from accessing YouTube. People would flock to an alternate service asap and you’ve would finally die

      • klyde@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        21
        ·
        1 year ago

        Just another Firefox fan boy. They do this shit when as blockers get brought up too as if Brave, Vivaldi, etc isn’t going to strip out the ad blocker nonsense when they build their versions. Just because these versions use Chromium as a base in no way means they have to use their code. Firefox fan boys are too busy talking about Firefox to understand this.

    • Excel@lemmy.megumin.org
      link
      fedilink
      English
      arrow-up
      16
      ·
      1 year ago

      Except WEI is going to make it so the website can detect and block you if you don’t allow the ads, regardless of your browser and extensions

      • igorlogius@lemmy.world
        link
        fedilink
        English
        arrow-up
        21
        ·
        edit-2
        1 year ago

        At the moment WEI has been rejected by mozilla, so it wont be implemented into firefox. if google decides to add it into chrome and to their services, they will effectively lock out all firefox users. - A very anarchistic part of me actually would like to see how that would play out … but at the moment i am unsure if google would actually dare doing this, but i guess, it will only be a matter of time and we’ll find out.

        Not sure if this move would actually damage the open web … since basically google would single itself out as the enemy … and i dont see many users appreciating such a move.

        But if the worst happens and the whole web follows googles example, i guess we can just call this iteration of a “open web” a failure and start over with something much simpler … maybe something like the gemini protocol as its base, which isnt polluted with clientside javascript garbage and bloated CSS/XHTML parsers and rendering engines .

        • Ubermeisters@lemmy.zip
          link
          fedilink
          English
          arrow-up
          10
          ·
          1 year ago

          I fully expect that without a change of current course, Google will ensure yt will just stop working on Firefox at some point.

          • arthurpizza@lemmy.world
            link
            fedilink
            English
            arrow-up
            14
            arrow-down
            2
            ·
            1 year ago

            I guarantee there will be a workaround. It’s not magic it’s just code. And once that code is on your machine there’s not much they can do about it.

            • igorlogius@lemmy.world
              link
              fedilink
              English
              arrow-up
              2
              ·
              edit-2
              1 year ago

              With streaming media they created this tiny DRM blob (you might have have heard of widevine.drm) which every browser needs to have to decode certain types of streaming media. Now imagine if something like that would be required … the website would only be loaded and rendered if the module would “validate” that nothing has been tampered with (think: signing and checksum validations). - Suddenly no more content filtering/adblocking or maybe just enhancing websites with userscripts. That is the web google is trying to create. Totally under their control and static. The user will again just like with television be a receiver without any influence. I personally find this to be a very scary, degrading and sad thought so much … that i would likely turn my back on this kind of web as much as possible and look for other networks (maybe something like i2p, gemini , … )

              • arthurpizza@lemmy.world
                link
                fedilink
                English
                arrow-up
                1
                ·
                1 year ago

                I don’t see the W3C or any of Google’s competitors jumping on board to give Google the keys to the web.

                • igorlogius@lemmy.world
                  link
                  fedilink
                  English
                  arrow-up
                  2
                  ·
                  edit-2
                  1 year ago

                  With chromes marketshare, they basically already have one half of the keys. If they can get a significant amount the server/backend owners to adopt/use their “features” (maybe lie like they tried with MV3 that it’s all about security and keeping bad actors out) … it’s game over.

      • Draconic NEO@lemmy.world
        link
        fedilink
        English
        arrow-up
        13
        ·
        1 year ago

        Purge and update your filter cache, check to make sure you have Anti-adblock filters enabled. If that doesn’t work do some troubleshooting with the extensions, one user found that other extensions were interfering and after disabling the problematic extension it worked.