lorendsr

Potential future abuse, whether due to laws becoming more permissive or a radical in-agency culture change that led to more people ignoring the law, is certainly concerning. As are current abuses. I just believe that the capabilities provided under the powers currently given to the agency are worth the abuses and potential future abuse. If I thought there was much chance that in the future, law enforcement and intelligence would not remain separate, my decision would change. I would prefer to live in a free unsafe state than a police state.

Vimium is mainly for in-page keyboard interactions (like opening a link or scrolling down). Ferro is for interacting with Chrome itself, for instance pinning a tab, saving/opening sessions, extension management, deleting bookmarks, etc.

Ferro does not suffer from the same keyboard shortcut problem as Vimium. Vimium injects code into every tab you have open (called "content scripts" in Chrome extensions) and uses javascript key listeners. Ferro uses the recently-introduced Chrome keyboard shortcut API. To manage your keyboard shortcuts for all extensions that use the API, go to "chrome://extensions" and click the "Keyboard shortcuts" link on the bottom-right.

Interestingly, Vimium's "Access your data on all websites" permissions can be less alarming than a similar notice only mentioning certain domains you care about, like stripe and coinbase.

Ferro creator here. The answer is of course no, Ferro was not looking at your coinbase or stripe data. It was only loading the API scripts from those domains asynchronously in order to reduce the load time of the options page, and to do so it needed those domains in the permissions list. I just published v1.0.9, in which I have switched it back to the slow version and removed the coinbase/stripe permissions from the manifest. Once you receive the update (<1 hr), you can visit `chrome://extensions/` and click the Ferro "Permissions" link to confirm. For more information, see https://github.com/ferro/ferro/issues/9

Broken again? Or maybe the interview was taken down.