3 ms·
I'm sorry if I came off as critical of your work. I did see you commenting on the extension support page and talked about it here[1]. I was pointing out the per
by ktta 10y ago
I'm sorry if I came off as critical of your work. I did see you commenting on the extension support page and talked about it here[1]. I was pointing out the permission model. I went into a little more detail here[2]. It's just how things are I guess.
Please don't let us security paranoid people stop you from contributing to open source software. And 6k+ users are using it with great reviews so you must already know your work is much appreciated. My gripe was about security practices, not about doubting the security of your specific extension. It is same problem with the way chrome handles all of the extensions' auto-updates.
[1]: https://news.ycombinator.com/item?id=13984773 https://news.ycombinator.com/item?id=13984773
[2]: https://news.ycombinator.com/item?id=13984661 https://news.ycombinator.com/item?id=13984661
- chrisl99 10y agoNo offence taken. we want the same thing - for Chrome to allow fine grain permissions. Although when I think about it, even a style sheet could be malicious to a degree (e.g. hiding important warnings, or adding misleading text)