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?
NS & Pale Moon
NS & Pale Moon
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Goanna/6.7 Firefox/102.0 PaleMoon/33.4.0.1
Re: NS & Pale Moon
NoScript is known to cause issues and not work in Pale Moon >= 33 - viewtopic.php?t=27128
*Always* check the changelogs BEFORE updating that important software!
Mozilla/5.0 (X11; Linux x86_64; rv:131.0) Gecko/20100101 Firefox/131.0
Re: NS & Pale Moon
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?
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Goanna/6.7 Firefox/102.0 PaleMoon/33.4.0.1
Re: NS & Pale Moon

Doesn't Pale Moon now hard-block NoScript?
https://noscript.net/changelog/
NoScript Classic versions prior to 5.1.8.7 have a security issue where websites could bypass script blocking, and it wasn't hard to exploit. IIRC that issue was introduced in the 5.x NoScript versions. I wouldn't use any NoScript Classic 5.x other than 5.1.9 in production.
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 @ https://classic.noscript.net/feed?classic&c=133
*Always* check the changelogs BEFORE updating that important software!
Mozilla/5.0 (X11; Linux x86_64; rv:131.0) Gecko/20100101 Firefox/131.0
Re: NS & Pale Moon
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 back to release 2.9?
"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 back to release 2.9?
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Goanna/6.7 Firefox/102.0 PaleMoon/33.4.0.1
Re: NS & Pale Moon
Sorry, I had understood that the crashing was universal for everyone running NoScript Classic in Pale Moon >= 33 and that using an older version of NoScript was somehow working around the problem for you. If that is not the case, disregard the suggestion to try NoScript 2.9.x.
*Always* check the changelogs BEFORE updating that important software!
Mozilla/5.0 (X11; Linux x86_64; rv:131.0) Gecko/20100101 Firefox/131.0
Re: NS & Pale Moon
I've never had any issues with NS in PM or in FF ESR 52.9.0.
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Goanna/6.7 Firefox/102.0 PaleMoon/33.4.0.1
Re: NS & Pale Moon
I thought PM in the last year or two took a U-turn on that hardcore policy on extensions because of all the backlash they got over it.
But I haven't followed the news over there much this year.
(I don't personally care any more because I got fed up with the toxic attitude of the developers of that project in general, along with its "stuck in time" technology platform.)
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36