5 ms·

I actually had the reverse chronology. I discovered how using ClickToFlash gave me significantly better battery life on my MBP, along with faster page loads and

I actually had the reverse chronology. I discovered how using ClickToFlash gave me significantly better battery life on my MBP, along with faster page loads and zero mysterious pinwheels. ClickToFlash has a better price-performance ratio than upgrading to an SSD – and I love my SSD. So when I got an iPad, I was especially mystified at why anyone should complain about this garbage being missing. edit: Useful links. Go grab ClickToFlash (Safari, OS X): http://clicktoflash.com/ http://clicktoflash.com/ Or the Safari extension for Mac or Windows: http://hoyois.github.com/safariextensions/clicktoflash/ http://hoyois.github.com/safariextensions/clicktoflash/ Or the Firefox equivalent: https://addons.mozilla.org/en-US/firefox/addon/flashblock/ https://addons.mozilla.org/en-US/firefox/addon/flashblock/

zdw 16y ago
rentzsch's clicktoflash is actually considerably out of date at this point. The new, Safari-extensionized version that is mentioned second is much better and updated frequently. (this link: http://hoyois.github.com/safariextensions/clicktoflash/ http://hoyois.github.com/safariextensions/clicktoflash/) (mathematical stickler: seeing as ClickToFlash is free, it's price/performance ratio is always zero)
- danilocampos 16y ago
  Haw, quite so. Still, even if the SSD were given to you for free, and we measured cost in installation time, the cost in time to install each one versus the resulting gains would be tremendously in favor of ClickToFlash, so awful is Flash.
feverishaaron 16y ago
Don't forget FlashControl for Chrome: https://chrome.google.com/extensions/detail/mfidmkgnfgnkihnjeklbekckimkipmoe https://chrome.google.com/extensions/detail/mfidmkgnfgnkihnj...
- 1880 16y ago
  I prefer enabling Click-to-play in about:flags.
  - CrazedGeek 16y ago
    Click-to-play doesn't let you disable it temporarily, which is a problem for some sites that rely on background Flash files. On Chrome, I prefer https://chrome.google.com/extensions/detail/gofhjkjmkpinhpoiabjplobcaignabnl?hl=en https://chrome.google.com/extensions/detail/gofhjkjmkpinhpoi...
    - 1880 16y ago
      I am not 100% sure if that extension is totally blocking the Flash files. Last time I checked it, it was only applying a "display: none" with CSS, and some files slipped past it, making it ineffective against 0-day exploits.
    - asb 16y ago
      I'm not sure I understand your meaning. Using just click to play in about:flags, on a page with blocked plugins you can click the icon which appears next to the bookmark star and select "Run all plug-ins this time". Is that not sufficient?
      - CrazedGeek 16y ago
        Ugh, I honestly hadn't noticed that. Maybe it wasn't enabled yet on the dev build or something. Still, per-site whitelisting is nice.
        elomar 16y ago
        For per-site whitelisting, you can click on that icon and check "always allow plugin on ..." or go to "settings > under the hood > content > plugins > manage exception." It isn't the easiest or most intuitive way, but so far worked well enough to me.

zdw 16y ago

rentzsch's clicktoflash is actually considerably out of date at this point. The new, Safari-extensionized version that is mentioned second is much better and updated frequently. (this link: http://hoyois.github.com/safariextensions/clicktoflash/ http://hoyois.github.com/safariextensions/clicktoflash/) (mathematical stickler: seeing as ClickToFlash is free, it's price/performance ratio is always zero)

danilocampos 16y ago
Haw, quite so. Still, even if the SSD were given to you for free, and we measured cost in installation time, the cost in time to install each one versus the resulting gains would be tremendously in favor of ClickToFlash, so awful is Flash.

feverishaaron 16y ago

Don't forget FlashControl for Chrome: https://chrome.google.com/extensions/detail/mfidmkgnfgnkihnjeklbekckimkipmoe https://chrome.google.com/extensions/detail/mfidmkgnfgnkihnj...

1880 16y ago
I prefer enabling Click-to-play in about:flags.
- CrazedGeek 16y ago
  Click-to-play doesn't let you disable it temporarily, which is a problem for some sites that rely on background Flash files. On Chrome, I prefer https://chrome.google.com/extensions/detail/gofhjkjmkpinhpoiabjplobcaignabnl?hl=en https://chrome.google.com/extensions/detail/gofhjkjmkpinhpoi...
  - 1880 16y ago
    I am not 100% sure if that extension is totally blocking the Flash files. Last time I checked it, it was only applying a "display: none" with CSS, and some files slipped past it, making it ineffective against 0-day exploits.
  - asb 16y ago
    I'm not sure I understand your meaning. Using just click to play in about:flags, on a page with blocked plugins you can click the icon which appears next to the bookmark star and select "Run all plug-ins this time". Is that not sufficient?
    - CrazedGeek 16y ago
      Ugh, I honestly hadn't noticed that. Maybe it wasn't enabled yet on the dev build or something. Still, per-site whitelisting is nice.
      - elomar 16y ago
        For per-site whitelisting, you can click on that icon and check "always allow plugin on ..." or go to "settings > under the hood > content > plugins > manage exception." It isn't the easiest or most intuitive way, but so far worked well enough to me.