-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Daemon appears to conflict with Google Chrome / Great Suspender plugin #3961
Comments
Were you using the IPFS Addon? |
No, I was not aware there is one. This should be promoted on the IPFS main web site. I'll post a link here to the web store for the convenience of others. Today I learned the developer's account was compromised and an unauthorized version of the extension was pushed to the Chrome webstore. It was merely by chance that I installed IPFS at the same time. The extension was updated silently in the background without my knowledge and permission. The issue is now resolved. As one user said: "Gotta love Google's walled garden with forced automatic updating of extensions and no way for the user to disable it without directly editing the extension's files. " |
We are creating https://github.com/ipfs/ipfs-companion/ which soon should work also on Chrome. Good that it was not issue on our side. Have fun discovering IPFS. |
Hold on, @h3298 what are you saying about account compromise? Please reach out to [email protected] asap. |
Ah okay, that's about a different extension unrelated to IPFS. For context: greatsuspender/thegreatsuspender#512 (comment) |
Version information: win64 0.4.9
Type: Bug, compatibility issue
Severity: High
Description:
90 suspended tabs were lost when launching daemon while browser was running
(this has never occurred before under any other circumstance)
a security warning also appeared in extensions list which has never been seen before
possibly a low memory issue was involved ; too busy to attempt replication at the moment due to loss of research project
idea: Can IPFS possibly be implemented in browser through an extension instead of the current method?
The text was updated successfully, but these errors were encountered: