this post was submitted on 21 Nov 2023
488 points (98.6% liked)
Firefox
17938 readers
3 users here now
A place to discuss the news and latest developments on the open-source browser Firefox
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That snippet of code is browser agnostic, which means you have the same problem on chrome lol
'not to worry, chrome will soon not have good adblockers, and those that remain will be crippled and have size-limited filter lists that must be distributed with the addon via our 'store'--meaning we can (and will at some point) shut down any filter updates that block our shit.'
Fair enough. I stopped using chrome a looong time ago so no problem anyway
From what I understand from the articles about this, it was found that different JavaScript code (without any delay added) was served in the HTTP response if Firefox was spoofed to look like the request came from Chrome, so it seems the issue only occurs on non-chrome browsers.
That’s fucked up for real
It seemed to be just a 5 second wait.
The weird part is that changing user agent to chrome seems to avoid it.
It's not weird. It's asshole design.