4 ms·
I think that the ability to filter out content is a basic right that should be built-in to any Internet application, not forced to be an "add-on" and vilified b
by makecheck 11y ago
I think that the ability to filter out content is a basic right that should be built-in to any Internet application, not forced to be an "add-on" and vilified by being seen as synonymous with attacks on the advertising industry and content providers.
And since regexes on URLs would be complicated and error-prone for most people, I think the onus is on content providers to throttle themselves, baked right into a user-agent protocol.
For example, the USER should be able to cage the provider with certain limitations that must be met in order for content to be displayed:
- "I am granting you no more than 500K of my data plan. Please send me a version of your page that meets these requirements."
- "I am granting you no more than 1% of my battery per week. If your site exceeds these requirements, your site will feature prominently as the cause of battery problems in a report that is periodically presented to your users."
- "I do not consider this site to be an 'application' so I have restricted several dynamic behaviors. Please send me a version of your page that can operate in a quarantined scripting environment."
And of course, browsers would be expected to provide sane defaults for these settings.
This approach isn't particularly hostile to any one industry; it doesn't specifically block ads (if they fit in that 500K, be my guest).