Firefox extensions - the downside

I'm a huge fan of Firefox extensions; it's high on the list of reasons to never stop using the browser. But there's always a downside, and my paranoid side has found it.

I love the Greasemonkey extension; try it and you'll find so many uses you'll wonder how you can write your own. Greasemonkey has one weakness, however; it runs on Javascript.

After installing the NoScript extension, which blocks all Javascript on a page, I found this weakness. You can't run Greasemonkey scripts on pages that you don't allow Javascript to run on. I noticed it when I went to BoingBoing's home page. There's a Greasemonkey script that strips out all the non-content on BoingBoing. NoScript blocks it.

If there were a way to allow Greasemonkey scripts, that would be ideal. However, that requires two independent developers to collaborate and continue to work together as features change or are added, a likelihood that's pretty low.

I'll be getting rid of NoScript; it was an experiment anyway. It's just disappointing to see good ideas step on each other.

No comments:

Post a Comment

What is that noisy IoT device on my network?

That's the first question that popped up when I installed AdGuard Home on my Raspberry Pi last night. Within minutes, hundreds of querie...