FoxReplace substitute targetting PM? Topic is solved

[Mæstro]

While looking through my extensions, I could see that FoxReplace (0·17·3) is the only one with an orange dot beside it. It is a small thing, but has a successor or substitute targetting Pale Moon ever been released? Nothing is wrong with FoxReplace, but it would be a small milestone in my Pale Moon history to be able to use only PM-specific extensions.

[moonbat]

has a successor or substitute targetting Pale Moon ever been released?

Nothing similar on the addons site? If the extension works fine then it shouldn't matter.

[adoxa]

Here's 0.17.3 with an updated install.rdf to include Pale Moon's id (there didn't seem to be anything in 1.x worthwhile including, other than being restartless; didn't bother looking at 2, since that's WebExtension only).

[moonbat]

I mean, other than adding Pale Moon as a target application. Since support for both Firefox and PM IDs has been retained after reverting the controversial Tobin initiated move to stop supporting the Firefox ID about 4 years ago.
If the extension works fine with no problems then there's no need to change the target ID unless someone is willing to become a full time maintainer (and that would run into branding and licensing issues as well)

[Moonchild]

IMHO it's better to not just add a Pale Moon ID to install.rdf without actually having someone maintaining it. The indicator is a reason to keep in mind it's unmaintained and serves a purpose. I get it's an OCD/ADHD thing and such to be annoyed by one odd indicator in a list but it's there for a reason.

[Mæstro]

Moonbat and Moonchild, you are both right that it is not that big a deal, hence ‘it is a small thing’. I thought to try experimenting with: an old Greasemonkey script as a substitute, manually editing the blacklist to permit words which are not profanity (such as vagina) or for which the ordinary meaning is far more important to me than any vulgar use in slang. Unfortunately, this script seems to fail in Pale Moon. Even so, this experiment has brought my attention to the fact that, now that I no longer browse Reddit through proxies or otherwise, I encounter foul words far less than before, such that I doubt I still need a profanity filter to spare myself headache. Discovering my needs for my browser have changed settles the matter (it is too trivial to call it a problem) just as well as any technical remedy.

[UCyborg]

Moonbat and Moonchild, you are both right that it is not that big a deal, hence ‘it is a small thing’. I thought to try experimenting with: an old Greasemonkey script as a substitute, manually editing the blacklist to permit words which are not profanity (such as vagina)

Off-topic:
I'd add foreskin too (though more precise term is prepuce).

I wonder how many times word vagina is used when the person really meant vulva.

That script accumulated a lot of years, especially from JavaScript's point of view. Reminds me of how some people like challenging themselves in what they could do with language features of the time.

I imagine version of the script written today would use MutationObserver to handle dynamically loaded content.

IMHO it's better to not just add a Pale Moon ID to install.rdf without actually having someone maintaining it. The indicator is a reason to keep in mind it's unmaintained and serves a purpose. I get it's an OCD/ADHD thing and such to be annoyed by one odd indicator in a list but it's there for a reason.

I like to put it on every extension I modify as a stamp of "It works on Pale Moon!".