This CL moves the base::Feature from content_features.h to
a generated feature from runtime_enabled_features.json5.
This means that the base::Feature can be default-enabled
while the web API is co...
Basically, if your browser modifies a web page in any way (such as by blocking ads, applying a theme, disabling javascript, whatever), the server would be able to detect this and deny access.
Google is pushing some bullshit that would allow websites to check if a client (you, your browser, your device) is on the okie-dokey list. If yes, you may enter e. g. Youtube, if not the you’re out. It’s like a bouncer for websites and of course Google would be that bouncer. So you might stand out in the rain if you are using one of the following:
deleted by creator
DRM for the web.
Basically, if your browser modifies a web page in any way (such as by blocking ads, applying a theme, disabling javascript, whatever), the server would be able to detect this and deny access.
You will use the web as google said or you won’t use it at all.
Basically drop „don’t be evil“, split to Alphabet, wait a few years, be evil
Google is pushing some bullshit that would allow websites to check if a client (you, your browser, your device) is on the okie-dokey list. If yes, you may enter e. g. Youtube, if not the you’re out. It’s like a bouncer for websites and of course Google would be that bouncer. So you might stand out in the rain if you are using one of the following:
VPN
Adblock
Non-Chromium browser like Firefox
This video by Louis Rossman is a pretty good explainer https://yewtu.be/watch?v=0i0Ho-x7s_U