this post was submitted on 20 Nov 2023
2654 points (98.0% liked)
Technology
59709 readers
2939 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Not trying to defend Chrome here as I dislike their other behaviours, but just from what's presented in the video, an alternative explanation would be caching. That is, when the reloading is triggered by the switch of user-agent, the cache is reused and thus a shorter load time.
To exclude this effect, the user needs to either
Have you seen this?
https://feddit.it/pictrs/image/0e13c670-4966-4073-89df-f042fe9cc6de.webp
Yes. I'm not a frontend dev, so not familiar with JS code (let alone an obfuscated fragment), but according to this HN comment, it's used for a different ad block detection function.
That makes a lot of sense. It’s still exclusive to Firefox, though