Skip to content
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

Chrome port #1

Open
jstrieb opened this issue Feb 5, 2021 · 0 comments
Open

Chrome port #1

jstrieb opened this issue Feb 5, 2021 · 0 comments
Labels
help wanted Extra attention is needed

Comments

@jstrieb
Copy link
Owner

jstrieb commented Feb 5, 2021

I began working on a Google Chrome port of the extension in the chrome branch, but quickly hit a wall due to limitations in how much the chrome.storage.local API is allowed to store for an extension. Everything else seems to work, except for storing 16MB+ Bloom filters (which raises exceptions).

Note that in this port, I still request the unlimitedStorage permission in the manifest.json file, but Chrome doesn't seem to be respecting it.

"unlimitedStorage"

For reference on why unlimitedStorage might not be working in Chrome, see the following references:

I am opening this issue as a place for discussion about how to overcome these storage limitations so that the extension can be ported to Chrome with as few changes as possible.

@jstrieb jstrieb pinned this issue Feb 5, 2021
@jstrieb jstrieb added the help wanted Extra attention is needed label Feb 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant