New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
“Too many” permissions required #366
Comments
Agreed, nowhere on the webstore page does it mention why these permissions are needed. Stumbled upon this as I'm trying to figure out why they are needed. |
I am actually freaked out enough by these that I have chosen not to update until I see some kind of explanation. I bet I'm not the only one. |
I freaked out and disabled it too. On the Chrome webstore Ilya replied to my request for info saying that the new bookmarks (b and B) are the reason. I trusted him enough to re-enable it. The new bookmarks are cool. Still wish Chrome extension permissions weren't so wide open. And wish the explanation preceded the question. |
Thanks bheckel. I'll trust him too! |
Vimium needs to access "Your data on all websites" and "Your browsing history" for the b and B keys to work on your bookmarks? I don't think it's ok that a new software update suddenly requires access to with no explanation offered. And that the only explanation offered (upon request) is that it's to access bookmarks? I don't find that a satisfactory explanation. |
Yes it's unfortunate that Chrome has sort of alarmist messaging around these permissions. I'll add a notice at the top of the Chrome web store page. "Your data on all websites" is really just Vimium asking for its javascript to run on every page you load. Theoretically we could steal everything on the page by doing so but we don't and never will. "Your bookmarks" is obviously necessary for us to offer the bookmark feature. The code is open source. Read it if you're paranoid. We don't communicate with any servers. Do you really think I wrote this Vim browser extension for nefarious purposes? |
|
Up to this point they are pretty obvious though assuming you utilize a wide array of commands of Vimium.
I am just an average user and know nothing about coding, but as I see and use it, apparently they are most what Vimium is expected being able to do so it naturally needs those permissions. |
The new version of Vimium (1.28) was automatically disabled by Chrome because it required additional permissions.
It would be nice if it included a short notice on why these permissions are in fact required.
This may simply be Chrome’s formulation but this sounds like an awful lot of trust I’m placing in a plugin that should “merely” hook to certain keystrokes.
Note: I’m not objecting to the fact that Vimium requires these permissions. I’m merely pointing out that it sounds scary, and should be properly explained to the user, lest it creates a culture of always clicking “OK”, no matter what data a plugin wants to access (which is precisely what Chrome wants to prevent, for good reasons).
The text was updated successfully, but these errors were encountered: