Firefox users are reporting an 'artificial' load time on YouTube videos. YouTube says it's part of a plan to make people who use adblockers "experience suboptimal viewing, regardless of the browser they are using."

you are viewing a single comment's thread
view the rest of the comments
[–] 631 points 2 years ago (7 children)

"They're the same picture."

Also, that does not explain why:

  • Chrome users who use an adblocker don't get the issue
  • Firefox users who do not use an adblocker get the issue
  • FIrefox users who use an adblocker, but change User Agent to Chrome, don't get the issue

Now, if only we knew who made Chrome and YouTube... The mind boggles.

  • source
  • hideshow 14 child comments
  • [–] 170 points 2 years ago (4 children)

    Given that Google's been talking about switching Chrome to a new plugin format that would limit the ability of adblockers to function on Chrome, and given that Google owns Youtube and profits from the ads Youtube displays...

    Nope, I'm not connecting the dots. Not sure why Google would be wanting people switch from Firefox to Chrome at this time.

  • source
  • parent
  • hideshow 8 child comments
  • [–] 63 points 2 years ago (4 children)

    It's more obvious than that even; their SEC paperwork states that adblockers are a risk to their profits. That's more than enough info to assume they're going to go to war in the near future (now) with them.

  • source
  • parent
  • hideshow 8 child comments
  • [–] 38 points 2 years ago

    They've always been at war with ad blockers. It's just most major multinationals have matured or diversified to a point where they are functional monopolies, and no longer gain any value in competition or service improvement.

    At this stage of the merger and consolidation phase of global capitalism, with captured governments that won't dare break them up or fine them more than a meek virtue signal, the most cost effective way to satiate the infinite growth of capitalism is to increase the exploitation and value extraction of their existing user base as much as possible (aka enshittification).

  • source
  • parent
  • [–] 32 points 2 years ago

    Just for clarity, they already switched protocols (Manifest v3), they just have continued to support the old format (v2) that allows unlock origin to work. They are discontinuing support for v2 next year.

  • source
  • parent
  • [–] 81 points 2 years ago (1 child)

    The last scenario is clearly a breach of anti-trust laws. It is time for alphabet to be broken up. Their monopoly is way worse than AT&T every was.

  • source
  • parent
  • hideshow 2 child comments
  • [–] -5 points 2 years ago (3 children)

    Alphabet's monopoly is bad, make no mistake.

    But they aren't controlling all electronic means of communication for 90% of the continental United States, as AT&T did in the ma' bell and pa' bell days.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 31 points 2 years ago (1 child)

    But they aren't controlling all electronic means of communication for 90% of the continental United States, as AT&T did in the ma' bell and pa' bell days.

    Google controls over 90% of the search business in the US and that's the way the vast majority of people begin their browsing. It's why US v Google is currently in the courts

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 2 years ago (1 child)

    MS vs US back in the 90's did not result in anything significant. This pretty much will happen again with Google. Some lobbyists will just do their thing, some minor slaps in the wrist and concessments between DoJ and Alohabet etc and Google will continue to Googling around.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 30 points 2 years ago (2 children)

    Also, that does not explain why:

    Chrome users who use an adblocker don’t get the issue
    Firefox users who do not use an adblocker get the issue
    FIrefox users who use an adblocker, but change User Agent to Chrome, don’t get the issue
    
    

    I am a Firefox user who uses adblock and I don't get the issue.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 24 points 2 years ago (2 children)

    I think uBlock might already be blocking that code.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 8 points 2 years ago (2 children)

    What do you mean by change user agent to chrome? Asking 4 a friend

  • source
  • parent
  • hideshow 4 child comments
  • [–] 24 points 2 years ago (3 children)

    For a specific how to, there's a bunch of firefox addons that do it, but the mozilla recommended one is this

    https://addons.mozilla.org/en-US/firefox/addon/user-agent-string-switcher/

    It's super easy to use, just open it and it gives a bunch of options.

    This is my current (fake) user agent;

    Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36

    With two or three clicks, this is my new (fake) user agent;

    Mozilla/5.0 (X11; CrOS x86_64 14541.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36

    A few more clicks;

    Mozilla/5.0 (Linux; Android 10; HLK-AL00) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.5112.102 Mobile Safari/537.36 EdgA/104.0.1293.70

    And finally;

    Mozilla/5.0 (compatible; MSIE 10.0; Macintosh; Intel Mac OS X 10_7_3; Trident/6.0)

    Now, that last one is making it look like I'm using internet explorer... Youtube videos will not load with that last one active. Claims my browser is too old and not supported.

    I don't know why they all start with Mozilla/5.0 but the apparently a lot of websites will block your requests if you don't have it (or a valid browser strings like it?)

  • source
  • parent
  • hideshow 6 child comments
  • [–] 18 points 2 years ago

    Almost all user agent strings start with that Mozilla prefix because Mozilla made the first browser with "fancy" features, so in the early internet many websites checked for that string to determine if they should serve the nice website or the stripped down version. Later when other browsers added the features, that also had to add that to their user string so users would get the right site. Which just cemented the practice.

  • source
  • parent
  • [–] 16 points 2 years ago

    Just a reminder to not use user agent switcher unless it's absolutely necessary, and if you do, limit it only for certain sites that need it. If enough people change their user agent, website operators will be like "See, no one use Firefox anymore. We shouldn't bother to support it anymore".

  • source
  • parent
  • [–] 10 points 2 years ago (1 child)

    I don't know why they all start with Mozilla/5.0 but the apparently a lot of websites will block your requests if you don't have it (or a valid browser strings like it?)

    This is a good summary of this mess: https://webaim.org/blog/user-agent-string-history/

  • source
  • parent
  • hideshow 2 child comments
  • [–] 7 points 2 years ago (3 children)

    When you browse to a website, your browser passes info about itself to the server hosting that site. This info is intended to help the server provide the best rendering code for your browser. This is called your User Agent.

    However, Google is using it here to identify Firefox users, and is apparently choosing to lump them all in a box called "adblock users" instead of trying to identify an ad blocker more accurately.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 8 points 2 years ago*

    That's because they may use code to detect as blockers that is not legal in the EU, so they might have thought that they're super crafty and used markers such as user agent for their cool coercion delay code thingy

  • source
  • parent
  • [–] 6 points 2 years ago (1 child)

    To add on

    You can spoof this user agent to see if a website does something shady depending on which browser you're using.

    So if you keep all other variables the same, and just toggle the user agent value, YouTube behaves differently

  • source
  • parent
  • hideshow 2 child comments
  • [–] 5 points 2 years ago (1 child)

    Supposedly Firefox users spoofing the Chrome user agent don't get the issue because the script tries to execute the 5s delay in a way that works on Chrome but not on FF. Because the Chrome method doesn't work on FF, it just gets skipped entirely. But I'm not sure if that's entirely accurate, just read about it.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 9 points 2 years ago (3 children)

    But then shouldn't there be a delay when using actual Chrome?

  • source
  • parent
  • hideshow 6 child comments
  • [–] 1 point 2 years ago (1 child)

    My understanding is the method they can use on chrome is near instant, but the alternative they use on Firefox is slower, hence the delay. Is this BS? Yeah probably, but it does at least logically follow.

  • source
  • parent
  • hideshow 2 child comments