InformAction Forums

I've never had any issues with NS in PM or in FF ESR 52.9.0.

I installed 5.1.9 in PM by dragging the XPI in. Not crashing the browser at this point. "If older NoScript versions don't break Pale Moon for you, and if you can circumvent the blocklist entry, you could try a 2.9.x NoScript version: Old NoScript Classic" Why would i want to go all the way...

PM is working now with the very old 5.0.6 release. Is this adequate in terms of the basic script blocking that NS does until I figure out what browser i am going to switch to permanently?

I've finally updated from old, old FF 52.9.0 ESR to Pale Moon x64 33.4.0.1.

I am running a way old version of NS (5.0.6). Can I upgrade to the latest NS version? Will it run in PM given how much they have complained about NS in the past?

I can't tell if those messages are being cut off. If not, it looks like a false positive to me. Did you try this exception? - ^https://c\.lytics\.io/ It looks like a tracker to me, so I would suggest additionally blocking it with either ABE or an adblock type addon. I put the exception in and this ...

In Palemoon. Just started. Really slowing down everything. How do I eliminate the msg? Tried to put an exception in the XSS options but that didn't seem to work for me. Trapped this from the console. Don't know if I grabbed the right part. [NoScript InjectionChecker] JavaScript Injection in ##page_n...

A lot of people are tired with the directions that Mozilla has been taking Firefox and so some have migrated to PM.

Would it really be that hard to make NS compatible with PM add-on requirements?

Or maybe we have to look at other solutions such as Umatrix?

Again, the Pale Moon people will probably be more helpful than we can be. I received this reply on the PM forums: Re: Noscript update Postby Lootyhoof » Sun Mar 12, 2017 10:26 am NoScript's minVersion on AMO is higher than 27.9. Thus, it will not auto update for us. Additionally, note that version ...

Could you translate that into something that a non-programmer could understand?

I received this replay on the PM forums when I asked why NS was not getting auto updated: "I would say because of compatibility. Pale Moon use Firefox 27.9 as useragent for AMO, so if a addon say the min-gecko is higher then 27.9 you doesnt get a update.' https://forum.palemoon.org/viewtopic.ph...

https://noscript.net/feed?t=a FF says "Firefox prevented this site from asking you to install software on your computer" PM says "This add-on could not be downloaded because its origin could not be verified" Chrome and IE 11 just show XML. I tried copying the actual XPI link and...

OK but assuming it does not work for me, how do I find this 2.9.5.3 release?

Some here contend 5.0 NOT fully compatible in PM.

http://www.ghacks.net/2017/03/06/noscri ... -released/

I have Pale Moon 27.1.2 (32bit) running. I just noticed that NS seems to be stuck back on v2.9.0.14, last updated 10 Aug 2016. It appears that v2.9.5.3 is current version per another post here that I saw. WHY is my PM not updating NS? And where can I find the v2.9.5.3 release, if that is the one I a...

I did nothing and the alerts went away. So I guess this was PM at work. People must have complained to them.

Having two different processes doing XSS filtering seems like a recipe for problems.

Perhaps NS should ID your msgs with an "NS" at the left?