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...
excuse my ignorance again, but how would monitoring software use in real time be different than how they currently monitor it? what would it really entail? serving more accurate ads and collecting/selling that more invasive type or information?
i haven’t looked into privacy much prior to joining lemmy, so i’m not very knowledgeable, but i’m very interested in learning more about it.
Not much, which is why this isn’t really a privacy issue. Privacy is already long gone. It’s a control issue.
Think about how many websites use Google Adsense. With this DRM, Google could force those websites to serve content only to users using chromium, and specifically those without adblockers installed. They’re trying to subjugate the internet.
excuse my ignorance again, but how would monitoring software use in real time be different than how they currently monitor it? what would it really entail? serving more accurate ads and collecting/selling that more invasive type or information?
i haven’t looked into privacy much prior to joining lemmy, so i’m not very knowledgeable, but i’m very interested in learning more about it.
Not much, which is why this isn’t really a privacy issue. Privacy is already long gone. It’s a control issue.
Think about how many websites use Google Adsense. With this DRM, Google could force those websites to serve content only to users using chromium, and specifically those without adblockers installed. They’re trying to subjugate the internet.