Nobody can even state that it’s actually happening “for competitive browsers” as even Chrome users are reporting an unexplained lag/slowdown. At this point, it’s just wild speculation and bandwagoning.
You absolutely can tell what’s happening by reading the source code. They are using a listener and a delay for when ontimeupdate promise is not met, which timeouts the entire connection for 5 full seconds.
They don’t need to put incriminating “if Firefox” statements in their code – the initial page request would have included the user agent and it would be trivial to serve different JavaScript based on what it said.
It’s not wild speculation as there is compelling, if incomplete, evidence. And to describe everyone’s reaction as “bandwagoning” is ridiculous. Firefox and Mullvad are my daily drivers. This directly impacts me. The fediverse is going to have a disproportionate number of non-chrome users.
I’ve duplicated it on 4 machines across 3 OS’s (windows 11, macOS, steamOS). Glad you got lucky. I’m sure you’re also familiar with A/B testing but if not I’m happy to explain it.
It is absolutely possible there is a reasonable explanation but for you to say 1) nothing is happening and 2) it’s “bandwagoning” is, again, ridiculous. Especially if your evidence is “well mine is fine,” which is not acceptable troubleshooting procedure.
Not all regions are served with the same scripts. That’s why the ad-block pop-up was shown for some users but not for others or at a later time for others. This also affected the update cycle of those anti-adblock scripts.
The reason for that is quite simple. New stuff is rolled out to only some users at first as some sort of beta testing procedure. If many people complain about functionality issues and all of those have the new version of the script, Google knows there is something wrong with it.
“It happens all the time” and “they always do *” is also comically unhelpful and useless. I’m getting a pot/kettle vibe from those that seem to take offense at my comment.
I mean you’re saying you want proof, don’t read the article, then say you don’t care because it works for you. Do you not understand why that’s a little perplexing? Anyway, I’ve said my piece. I don’t imagine it will be a very productive discussion. Have a good week.
Is this arguably anticompetitive and illegal?
Nobody can even state that it’s actually happening “for competitive browsers” as even Chrome users are reporting an unexplained lag/slowdown. At this point, it’s just wild speculation and bandwagoning.
You absolutely can tell what’s happening by reading the source code. They are using a listener and a delay for when
ontimeupdatepromise is not met, which timeouts the entire connection for 5 full seconds.https://pastebin.com/TqjzbqQE
I’m sorry but I don’t see how that check is browser-specific. Is that part happening on the browser side?
They don’t need to put incriminating “if Firefox” statements in their code – the initial page request would have included the user agent and it would be trivial to serve different JavaScript based on what it said.
Easy enough to test though. Load the page with a UA changer and see if it still shows up when Firefox pretends to be Chrome
Well, at least I learned that javascript understands exponential notation. I never even bothered to try that lol
It’s not wild speculation as there is compelling, if incomplete, evidence. And to describe everyone’s reaction as “bandwagoning” is ridiculous. Firefox and Mullvad are my daily drivers. This directly impacts me. The fediverse is going to have a disproportionate number of non-chrome users.
I also use FF solely and have no slowdowns on YT. I guess they like my copy of the browser.
I’ve duplicated it on 4 machines across 3 OS’s (windows 11, macOS, steamOS). Glad you got lucky. I’m sure you’re also familiar with A/B testing but if not I’m happy to explain it.
It is absolutely possible there is a reasonable explanation but for you to say 1) nothing is happening and 2) it’s “bandwagoning” is, again, ridiculous. Especially if your evidence is “well mine is fine,” which is not acceptable troubleshooting procedure.
Not all regions are served with the same scripts. That’s why the ad-block pop-up was shown for some users but not for others or at a later time for others. This also affected the update cycle of those anti-adblock scripts.
The reason for that is quite simple. New stuff is rolled out to only some users at first as some sort of beta testing procedure. If many people complain about functionality issues and all of those have the new version of the script, Google knows there is something wrong with it.
“works fine on my machine lol” is unhelpful and useless.
It’s very well known that Google makes heavy use of a/b testing. They did it with the adblock block and they’re doing it with this
“It happens all the time” and “they always do *” is also comically unhelpful and useless. I’m getting a pot/kettle vibe from those that seem to take offense at my comment.
Where’s the proof? Note: I didn’t read the article
Then read it?
no thanks… I havent had any issues… been using firefox since v1.0
I don’t really understand what you’re trying to do lol
Ok
I mean you’re saying you want proof, don’t read the article, then say you don’t care because it works for you. Do you not understand why that’s a little perplexing? Anyway, I’ve said my piece. I don’t imagine it will be a very productive discussion. Have a good week.
Then why did you ask for proof lol