3 ms·
I’m personally not upset just worried about the fact that security is now a huge risk because you’re having to trust an extension creator that has access to you
by benjaminjackman 7y ago
I’m personally not upset just worried about the fact that security is now a huge risk because you’re having to trust an extension creator that has access to your entire browser history or worse and who is one auto-update from turning to spy or malware.
You also have a discovery problem having to wade through multiple options increasing your surface area to malware exposure.
IIRC this isn’t even theoretical it’s happened with ones that replaced user style sheets, another “unused” feature that was gradually deprecated.
Maybe the best way forward is to take an apple iPhone approach and have official extensions, similar to the apps that come with the iPhone like the podcast one.
Then when these features are removed they are instead moved to an official extension. Thereby mitigating the security risk and alleviating the discovery problems.
The community can take over these extensions and you have a starting point to personally adapt and fork them that is a lot simpler and faster than trying to maintain a browser fork.
Further the browser maker can more directly see usage of these feature replacing extensions
And finally, when removing features ensure the extensions api has the power to support their replacement.