3 ms·

I read somewhere Youtube used to send a response like {..., ads: [1, 2, 3]}. uBlock would see this response and turn it into {..., ads: []} and load the page ac

I read somewhere Youtube used to send a response like {..., ads: [1, 2, 3]}. uBlock would see this response and turn it into {..., ads: []} and load the page accordingly. I guess now, Youtube expects a response back, and occasionally, the request/response is faked. So, when uBlock adjusts the request/response and says "This user watched the ads", Youtube knows the request/response was fake and there were no ads to begin with, notifying that user is using an adblocker.

krackers 3y ago
Looking at the filters that uBlock is using, it still seems to be some sort of regex on the xhr request/response body [1]. Why can't youtube trivially defeat this by encrypting everything? It seems like trying to go about the cat-mouse game in this fashion in a losing battle, because all google needs to do is just change up the names a bit each day. [1] https://github.com/uBlockOrigin/uAssets/commit/fb33bb3c1fa99db4be4e7a3e9f76ecfe58a25444 https://github.com/uBlockOrigin/uAssets/commit/fb33bb3c1fa99...
- LelouBil 3y ago
  > It seems like trying to go about the cat-mouse game in this fashion in a losing battle, because all google needs to do is just change up the names a bit each day. That's exactly what they are doing, well I don't know about only "change up the names" but they update the script multiple times per day and uBlock Origin devs are trying to catch up.