3 ms·

> It can: > * Read and change all your data on the websites you visit https://github.com/adam-p/markdown-here/blob/master/src/manifest.json#L19 https://github

> It can: > * Read and change all your data on the websites you visit https://github.com/adam-p/markdown-here/blob/master/src/manifest.json#L19 https://github.com/adam-p/markdown-here/blob/master/src/mani... Shouldn't this just be email serving domains? e.g. `https://mail.google.com` https://mail.google.com` et al? Also it'd be great if the Chrome webstore could offer some verification, so that as long as I trust Github and Google, I can confirm that the code I see at Github is the extension I'm installing.

arkadiyt 9y ago
Chrome extensions are stored unpacked on your filesystem, it's easy to read what code is being used. On OSX they're in: ~/Library/Application Support/Google/Chrome/Default/Extensions
- chittti 9y ago
  Here's a script which makes it easier. https://gist.github.com/chittti/6f59b53053c44954414ff15d58265606 https://gist.github.com/chittti/6f59b53053c44954414ff15d5826...
adam-p 9y ago
> Shouldn't this just be email serving domains? That was my initial idea, but then I realized that it can work in more places than I ever would have guessed. And I/we wouldn't have discovered them if it were only whitelist-enabled. You can see dozens of the sites here, and there are surely many more: https://github.com/adam-p/markdown-here/wiki/Compatibility https://github.com/adam-p/markdown-here/wiki/Compatibility > Also it'd be great if the Chrome webstore could offer some verification I agree, in principle. Unfortunately, it wouldn't match. At some point Mozilla decided to start rejecting updates because there was unreachable -- Chrome-only -- code in the extension. So I had to start using a preprocessor during builds to strip out platform-specific stuff. (AMO's reviews have driven me nuts over the years.) The build is reproducible, though. I also provide instructions for running the extension directly from source. Chrome makes it easy (Firefox doesn't). https://github.com/adam-p/markdown-here#manualdevelopment https://github.com/adam-p/markdown-here#manualdevelopment (I just realized that I need to update the Firefox instructions/link for WebExtensions. Which is even more painful than XUL was to use from source.)

arkadiyt 9y ago

Chrome extensions are stored unpacked on your filesystem, it's easy to read what code is being used. On OSX they're in: ~/Library/Application Support/Google/Chrome/Default/Extensions

chittti 9y ago
Here's a script which makes it easier. https://gist.github.com/chittti/6f59b53053c44954414ff15d58265606 https://gist.github.com/chittti/6f59b53053c44954414ff15d5826...

adam-p 9y ago

> Shouldn't this just be email serving domains? That was my initial idea, but then I realized that it can work in more places than I ever would have guessed. And I/we wouldn't have discovered them if it were only whitelist-enabled. You can see dozens of the sites here, and there are surely many more: https://github.com/adam-p/markdown-here/wiki/Compatibility https://github.com/adam-p/markdown-here/wiki/Compatibility > Also it'd be great if the Chrome webstore could offer some verification I agree, in principle. Unfortunately, it wouldn't match. At some point Mozilla decided to start rejecting updates because there was unreachable -- Chrome-only -- code in the extension. So I had to start using a preprocessor during builds to strip out platform-specific stuff. (AMO's reviews have driven me nuts over the years.) The build is reproducible, though. I also provide instructions for running the extension directly from source. Chrome makes it easy (Firefox doesn't). https://github.com/adam-p/markdown-here#manualdevelopment https://github.com/adam-p/markdown-here#manualdevelopment (I just realized that I need to update the Firefox instructions/link for WebExtensions. Which is even more painful than XUL was to use from source.)