Warning: Some posts on this platform may contain adult material intended for mature audiences only. Viewer discretion is advised. By clicking ‘Continue’, you confirm that you are 18 years or older and consent to viewing explicit content.
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.
Yes absolutely. Your hardware has built in DRM capabilities. Modern CPUs basically have a 2nd small CPU inside that runs proprietary code and manages the primary CPU, and it also handles DRM.
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.
This sound scaring, but we have been working around DRM shit since it’s invention if I recall… Should we still be alarmed?
Yes absolutely. Your hardware has built in DRM capabilities. Modern CPUs basically have a 2nd small CPU inside that runs proprietary code and manages the primary CPU, and it also handles DRM.
That isn’t something you can easily work around.