-
Notifications
You must be signed in to change notification settings - Fork 969
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
Permission now requires "read and change all your data on all websites"? #1177
Comments
Yes, we changed the permission requirements for the following reasons:
Therefore, after referencing other AI extension products such as Monica, Sider.ai, etc., we changed to request broader permissions similar to theirs. |
Having full access to data may let users worried, even worse than clicking permissions. Is there a better way? |
I agree it is worrisome. I just paid for ChatHub Premium and now this sudden change is disappointing. |
I will also stop using this extension due to the extended permissions. A shame. |
Actually after more research, it seems an extension can be forced to be limited to only specific sites even if at first it requests access to any site. You can go to the extension settings and change site access to "Specific sites" and add sites manually. I have done so for the models that I want to use and it works fine. |
We hope to see good results so that we can confidently recommend ChatHub extention to those around us. |
@wong2 Considering @tomups post would you consider maintaining a list of all the domains required for chathub to work? I also don't feel comfortable allowing extensions to access every site I visit. If a malicious actor gains access to one of those extensions they can basically access every users banking. |
Gave permission to these domains, it seems to work for ChatGPT, Gemini, Claude, Copilot (free web access). Perplexity and Meta are not working.
|
Describe the bug
The latest version requires "read and change all your data on all websites"
Desktop (please complete the following information):
Is this a recent permission change? This feels overly wide compared with before?
Before:
The text was updated successfully, but these errors were encountered: