2 ms·
This has zero to do with privacy and security, because the APIs being removed only have to do with modifying pages, the ability to read data from pages is unaff
by throwaway2048 7y ago
This has zero to do with privacy and security, because the APIs being removed only have to do with modifying pages, the ability to read data from pages is unaffected. The only real consumer of these APIs are ad blockers, they are quite obviously being specifically targeted.
Painting this as all about user safety when it handsomely rewards Google's largest profit center is farcical. (the new static list of 50k filters will be completely trivial to workaround).
The only thing that is bogus here is the people denying it has nothing to do with ad blocking.
- privateSFacct 7y agoThe extensions that want to do blocking would then not need to request permission to read and modify pages. As users we could pick adblockers that didn't require permission to ready all our activity. How is reducing the required permissions (significantly) not an enhancement to user safety. Your argument that we always must give extension authors full permissions to get anything done is a pathetic one frankly.
- throwaway2048 7y agoChrome could easily enable this new API without crippling the old one, if that's what users really wanted (its not).