4 ms·
The problem with closing the API is that for even the most advanced users, it will now be impossible to get the (very useful) functionality these extensions pro
by ROARosen 5y ago
The problem with closing the API is that for even the most advanced users, it will now be impossible to get the (very useful) functionality these extensions provide.
- deleted 5y ago[deleted]
- jolux 5y agoI believe it was tptacek who once commented half-jokingly that the ideal thing to do would be to leave the API open to uBlock Origin exclusively and kill it for everything else. The privileges required by that extension and others like it are indeed very powerful and often abused. This is not a problem with an easy solution, your suggestions are essentially the status quo and the industry is beginning to move on from it.
- pmontra 5y agoMozilla went that way on Android when they broke all extensions about one year ago except a few blessed ones.
- shock 5y agoThere is now a way to enable any extension in Firefox Nightly.
- deleted 5y ago[deleted]
- skybrian 5y agoHmmm. I’m not implying anything here, but I’m wondering how we know we can trust uBlock Origin. How is its security vetted?
- ROARosen 5y agoHmmm. You're invited to vet it yourself here: https://github.com/gorhill/uBlock https://github.com/gorhill/uBlock
- skybrian 5y agoThis doesn't help if it gets sold to someone else, as many extensions have.
- jolux 5y agoIt’s open-source, and the author has a long history of supporting his product for free as an ethical good, even while some of his collaborators have went commercial and cashed out, once even taking the project name.
- the8472 5y agoThe issue with that approach is that the next addon developer who comes up with something as useful as uBlock will not be able to develop that. Legacy carveouts protect past innovations but not future ones.