-
Notifications
You must be signed in to change notification settings - Fork 42
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
Reinstate archiveror to chrome addon store ? #57
Comments
What's unsafe about it? |
How do you install the extension manually? |
@bigsmile01 I was able to load the extension in Chrome. First, get the source of this repo then...
You should then see the extension loaded in Chrome. |
but is it safe, given the cause of delisting of archiveror? has someone
vetted the source code?
…On Thu, May 5, 2022, 9:56 PM Mat Kelly ***@***.***> wrote:
@bigsmile01 <https://github.com/bigsmile01> I was able to load the
extension in Chrome. First, get the source of this repo then...
1. Go to More Tools > Extensions in Chrome's ⋮ menu
2. Toggle the "Developer Mode" switch
3. Select the "Load Unpacked" button
4. Navigate to the src directory in the source of the repo
5. Click the select button
You should then see the extension loaded in Chrome.
—
Reply to this email directly, view it on GitHub
<#57 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACJSM5KEGIWTTUSNAKYYD3LVIPHP5ANCNFSM5CKW5LIQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Thanks! It installed. Although it doesn't seem to work. When I click "Archive Now" nothing happens. Any ideas? |
It looks like the extension uses some external dependencies (e.g., babel) via module imports, so likely needs more than the above procedure to be built. Some tutorials exist on packing extensions in this way but I am not familiar with doing so. Anyone that has experience packing extensions using imports (e.g., using yarn/webpack) might know more and hopefully can provide some insights here. |
I am guessing the extension got delisted from the Chrome Web Store either because the author failed to fill out the limited use form, or there are inconsistencies between the extension's privacy policy, the disclosures provided through the developer dashboard, and the behavior of the extension. The inconsistencies could be the result of:
@rahiel would most certainly know the reasons for the extension's removal from the Chrome Web Store if he/she consults the Troubleshooting Chrome Web Store violations guide. Other than the aformentioned violation of privacy, this extension seems safe: VirusTotal detected no malware. |
Tried to install .zip version(its available in other open issue's) and via that guide aka through .crm file, which didn't gave positive result, since it shown error |
Archiveror was removed from chrome addon store, will it be reinstated or to just install the extension manually.
The text was updated successfully, but these errors were encountered: