5 ms·

I get around that by downloading the extension source and then using Chrome extension developer mode to “load unpacked extension”. Then I’m confident the extens

by varenc 3y ago

I get around that by downloading the extension source and then using Chrome extension developer mode to “load unpacked extension”. Then I’m confident the extension won’t change on me. (But for this extension I don’t give it all site permissions anyway. I just enable on site by site basis)

quickslowdown 3y ago
That's terrible for security, but great for convenience :)
- varenc 3y ago
  Can you explain what you mean by this more?
  - zeofig 3y ago
    [flagged]
  - lukan 3y ago
    Probably because "no automatic updates means bad"? Which might be true in general, but maybe not here. Depends how complex the source is.
    - quickslowdown 3y ago
      This is exactly the point I was making. I personally don't care that this is how some people manage their chrome extensions. It's clever, and will help if the source suddenly changes. If there is a vulnerability in the version you've downloaded & keep installing, it'll never be fixed because no automatic updates. Plenty of examples of extension vulnerabilities in Chrome, but the stability of your plugins not auto updating is definitely appealing to avoid unexpected changes/behavior