• redcalcium@lemmy.institute
    link
    fedilink
    arrow-up
    44
    ·
    edit-2
    1 year ago

    Combine this with Chrome enforcing manifest v3 starting at June 2024, YouTube ads will be virtually unblockable on Chrome, even with an ads blocking extension installed because Google will be controlling the ad blocking mechanism used by the ad blocker. They can arbitrarily reduce the max number of the blocking rulesets, how often the extension can update the rulesets, or even elect to skip running any rulesets that target YouTube or Google domains.

        • Copatus@lemmy.world
          link
          fedilink
          arrow-up
          8
          ·
          1 year ago

          That’s sort of better for the people who migrate then, no?

          If the average user just decides to deal with ads that means it won’t be worth the effort to go after the minority of people who will be AdBlocking

    • TechNom (nobody)@programming.dev
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      They can arbitrarily reduce the max number of the blocking rulesets, how often the extension can update the rulesets

      The size is already just 50. Those who think that adblocking is possible with this is fooling themselves.

      or even elect to skip running any rulesets that target YouTube or Google domains.

      If anybody acts surprised when it happens, they’re probably too stupid to be allowed on the web.

  • jballs@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    28
    arrow-down
    1
    ·
    1 year ago

    I read in a different post that the code was misinterpreted to be a 5 second sleep before showing the video, but instead was waiting 5 seconds to execute some anti-ad-block script. Still pretty sleazy either way.

    • Solemarc@lemmy.world
      link
      fedilink
      arrow-up
      9
      ·
      1 year ago

      When I went rooting around to find it. I figured it was some QA process that starts 5 seconds after the video loads (the timer seems to be async and the code sends a promise off while it waits). Of course, it’s all minified JS so it’s a huge pain to read.

    • TechNom (nobody)@programming.dev
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      Facebook for all its nastiness was very much incompetent in influencing the direction of the web. Look at their failed attempts like free basics.

      Google on the other hand has the web tightly in its dirty grip. At this point, they aren’t even pretending to be nice. Even those plans that cause them reputational damage are brought back in some other name.

      The only way to stop Google is for the regulatory agencies to put their foot down hard. They should be divided into at least a couple dozen companies that are not allowed to do business with each other.

  • griD@feddit.de
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    3
    ·
    1 year ago

    I really like how my meme proliferates along this 'verse :) I hope the discussions ITT are as nice as in mine.