search

amasad / eHistory

A Google Chrome extensions that enhances the browser's history search and management in many ways.
https://chrome.google.com/extensions/detail/hiiknjobjfknoghbeelhfilaaikffopb?hl=en
MIT License
41 stars 9 forks source link

Why did Google ban this Chrome Extension? #26

Open a-raccoon opened 5 years ago

a-raccoon commented 5 years ago

eHistory 1.14 This extension violates the Chrome Web Store policy.

Did Google give any indication why they've banned this extension? I use it all the time.

amasad commented 5 years ago

No. And I didn't have time to follow up on it

farazmateen commented 5 years ago

This extension was pretty good.

Do you intend to bring it back.

Also, is there anyway I can run it as is? I mean through terminal or something?

amasad commented 5 years ago

Happy to transfer ownership to someone willing to revive it.

On Mon, Nov 5, 2018 at 9:47 PM farazmateen notifications@github.com wrote:

This extension was pretty good.

Do you intend to bring it back.

Also, is there anyway I can run it as is? I mean through terminal or something?

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/amasad/eHistory/issues/26#issuecomment-436138431, or mute the thread https://github.com/notifications/unsubscribe-auth/AAj2_knsOypPZuGpHNNPtQGl3N92muuxks5usSKBgaJpZM4Xa8TP .

forabi commented 5 years ago

Hey @amasad, I'd like to revive this extension. I really need that search by URL and delete all results feature!

a-raccoon commented 5 years ago

@forabi I would recommend making fork the project and then upload the extension to Google from your own account, given the logistic particulars at play here. That's probably the best route. Then @amasad can transfer/redirect github ownership later on once you've proven a working extension on the Chrome extension store.

amasad commented 5 years ago

@forabi I would recommend making fork the project and then upload the extension to Google from your own account, given the logistic particulars at play here. That's probably the best route. Then @amasad can transfer/redirect github ownership later on once you've proven a working extension on the Chrome extension store.

Sounds good