this post was submitted on 21 Nov 2023
486 points (98.6% liked)
Firefox
20351 readers
88 users here now
/c/firefox
A place to discuss the news and latest developments on the open-source browser Firefox.
Rules
1. Adhere to the instance rules
2. Be kind to one another
3. Communicate in a civil manner
Reporting
If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The user agent is in the request header, so it's known before any response is sent from YouTube.
I don't know if that's what they're doing, because it's not possible to know what their server code is doing, making it a far better place to hide sleazy code.
But the server outputs code for the browser to run. Doesn't matter what the server does as long as the browser gets there same output.
Server side they could stall based on the agent but it's not the case here. Whatever is happening seems to be client side.
The client code can be modified depending on the request headers before being returned by the server
They're looking at the code returned by the server with a chrome user-agent and it's the same.
They only said that snippet was present, not that all of the client code was the same