Skip to content
This repository has been archived by the owner on Mar 1, 2023. It is now read-only.

Look into publishing on Chrome Web Store #14

Closed
kkkrist opened this issue Oct 12, 2019 · 6 comments
Closed

Look into publishing on Chrome Web Store #14

kkkrist opened this issue Oct 12, 2019 · 6 comments
Assignees
Labels
enhancement New feature or request wontfix This will not be worked on

Comments

@kkkrist
Copy link
Owner

kkkrist commented Oct 12, 2019

https://developer.chrome.com/webstore/publish

@kkkrist kkkrist added the question Further information is requested label Oct 12, 2019
@kkkrist kkkrist self-assigned this Oct 12, 2019
@AGlezB
Copy link

AGlezB commented Nov 8, 2019

Chromium 80.0.3960.0 (Official Build) (64-bit) seems to require extensions to come from the store.
image

The Learn more page says: To protect you while you browse, Chrome only lets you use extensions that have been published on the Chrome Web Store.

I followed the install instructions in README.md. Did I miss something?

@kkkrist
Copy link
Owner Author

kkkrist commented Nov 8, 2019

Oh wow… thanks for bringing this up. Are you able to manually enable the extension with the switch (might require developer mode) or is it not possible at all?

I'm still on Chromium v78 (current stable), where I can freely install (and enable) the extension with and without developer mode enabled. I guess this is a change introduced in later versions, a rather controversial one to put it mildly. One of the reasons I use Chromium and not Chrome is to escape Google lock-in after all.

I'll investigate and see what I can do.

@AGlezB
Copy link

AGlezB commented Nov 8, 2019

Are you able to manually enable the extension with the switch (might require developer mode) or is it not possible at all?

Not possible at all. I though I was doing something wrong so I flipped the switch several times.

One of the reasons I use Chromium and not Chrome is to escape Google lock-in after all.

Same here.

I'll investigate and see what I can do.

Thanks a lot!

@kkkrist
Copy link
Owner Author

kkkrist commented Nov 10, 2019

@AGlezB I've updated the README with an alternate installation method which should work for you, see Installing via "Load unpacked extension".

Additionally I'll list the extension in the Chrome Web Store as soon as the PR for #16 lands. The fact that I use a proxy to circumvent CORS won't help to get through the review process, so that has to come first.

As to the root cause of the warning and whether it's something that's been introduced in Chromium 79 or 80, I can't tell. I've skimmed briefly through the source code and found the string itself (IDS_EXTENSIONS_ADDED_WITHOUT_KNOWLEDGE) included years ago. So the whole behaviour probably isn't new and triggered by some heuristics.

If anybody knows more, I'd love to hear!

@kkkrist kkkrist added enhancement New feature or request and removed question Further information is requested labels Nov 10, 2019
@AGlezB
Copy link

AGlezB commented Nov 11, 2019

@kkkrist It does work. Thanks.

@kkkrist kkkrist added the wontfix This will not be worked on label Apr 29, 2020
@kkkrist
Copy link
Owner Author

kkkrist commented Apr 29, 2020

Closing. I don't think I'll publish this extension on the Chrome Web Store in the near future. It'll probably draw more attention than I can handle right now. The proxy is already running on the limit of what of the current (free plans) hosting setup allows and I want to concentrate on other projects for now.

Anyway, the extension works fine as it is and I guess people really interested are fine with the manual/dev-mode install.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants