Reduce Fraidycat's web extension permissions. about fraidycat HOT 2 OPEN

Ok, this situation is getting worse: e08f800#diff-051a8a7bcae8db1e4cee8eb09b52e619

Added: webRequest and webRequestBlocking

The problem is that, up until now, I've been using the chrome-extension:// URL to run the browser app. So the background page runs the fetch requests and the app shows the state. The sendMessage API is used to communicate between the two.

Unfortunately, this setup causes #1 - the issue where a large feed can park the browser app until it completes. The problem is that the background page is also a chrome-extension:// URL, so it shares a VM with the app. In order to separate them, I moved the app to https://fraidyc.at/s/. This now solves #1 - which is a key issue for me.

I tried using Web workers - but I need the fetch API and the DOMParser() in the worker - so it's a no go.

In all, I feel like the extension API is a poor fit for Fraidycat in this regard. The only permissions I should actually need are:

• Making anonymous HTTP(S) requests.
• Hosting a browser app somewhere that doesn't share a VM with the background script.
• Unlimited storage.

Only the third one should require permissions! There is no way to ask for the first two.

from fraidycat.

On the first permission I listed (access to browser history and tabs), it looks like there is a possible solution by using an iframe: http://www.airovic.com/itsjustaniframe.html

However, one issue here is that JavaScript will run and the page will render. So this could result in drastically different HTML from the stuff gotten by fetch. Still, an option!

from fraidycat.