Comment on Get notified whenever there’s a new top post on Hacker NewsComments−Sephr11yObfuscated code plus these permissions isn't helping me trust you. As a Chrome extension developer, I can tell at a glance that many of these permissions are not necessary to implement the functionality as described. "permissions": [ "<all_urls>", "activeTab", "alarms", "background", "browsingData", "chrome://favicon/", "clipboardWrite", "contextMenus", "cookies", "declarativeContent", "fontSettings", "gcm", "identity", "idle", "notifications", "pageCapture", "power", "proxy", "sessions", "storage", "system.cpu", "system.display", "system.memory", "system.storage", "tabCapture", "tabs", "topSites", "tts", "unlimitedStorage", "webNavigation", "webRequest", "webRequestBlocking" ] Definitely not taking any chances installing this.−motoboi11yAsking full privileges is a way of avoiding changing them on a update.If you change permissions on a update, chrome will ask for user interaction.That being said, if you don't plan to broad the scope of an app or extension in the future, there is no point.This technique is applied on a lot of android apps too.−Sephr11yYeah, it's okay to do this as long as the developer explains in the app/extension overview that the permissions are for planned features.
Comments
Obfuscated code plus these permissions isn't helping me trust you. As a Chrome extension developer, I can tell at a glance that many of these permissions are not necessary to implement the functionality as described.
Definitely not taking any chances installing this.Asking full privileges is a way of avoiding changing them on a update.
If you change permissions on a update, chrome will ask for user interaction.
That being said, if you don't plan to broad the scope of an app or extension in the future, there is no point.
This technique is applied on a lot of android apps too.
Yeah, it's okay to do this as long as the developer explains in the app/extension overview that the permissions are for planned features.