Avoiding the Scunthorpe problem with FoxReplace Topic is solved

[Mæstro]

I dislike profanity and use FoxReplace to substitute foul words with em dashes. However, as named in the title, this can result in false positives: eg one reads of the ancient ‘Cu—es’. Would anybody have advice on how I can hide bad language I do not want to see while avoiding embarrassing mistakes like this?

[Gemmaugr]

Would seems like an exercise in futility, as "bad" words can be highly individual (some people are offended by the word fat or master), and slang constantly evolves (like sheite or shite or type shi even scheize instead of shit).

That said, would surrounding the words in their entirety with spaces like %20shit%20 make it so that it doesn't affect the word inside of another word?

[back2themoon]

Doesn't that extension allow you to replace "whole words" only? I use the following userscript for replacing words (not "bad" ones, just annoying spelling mistakes on a few websites).

https://greasyfork.org/en/scripts/10976 ... n-webpages

[Michaell]

Doesn't that extension allow you to replace "whole words" only?

Nope, it works on strings inside a word.

[Michaell]

I dislike profanity and use [url=https://j2team.dev/firefox-extension/foxreplace] Would anybody have advice on how I can hide bad language I do not want to see while avoiding embarrassing mistakes like this?

It's not what you're hoping for, but using a specific custom string you can recognize rather than dashes allows you to understand what was replaced. If the embarrassing part is when you're quoting someone else's text, just remember to proofread before posting, which is a good practice anyway.

[Moonchild]

using a specific custom string you can recognize rather than dashes allows you to understand what was replaced.

Profanity by any other sequence of letters is still profanity.

[Mæstro]

Would seems like an exercise in futility, as "bad" words can be highly individual (some people are offended by the word fat or master), and slang constantly evolves[…]

That said, would surrounding the words in their entirety with spaces like %20[example]%20 make it so that it doesn't affect the word inside of another word?

I am implementing this for myself, so only what offends me counts.
As cursing has become more socially acceptable, I never encounter deliberate misspellings as you describe. Using spaces seems to work: ‘Cushite’ and ‘shitake’ do not trigger the filter, yet your own examples do, to my pleasant surprise. If I must add inflected expletives to the blacklist, I think I can manage this. Indeed, I managed it with this post, adding filters for expletives followed by a full stop, comma or question or exclamatory mark.

[adoxa]

I'm not sure what version you're using, as neither 2.6.2 (WebExtension) nor 1.1.3 (installed, but the options don't show up) worked. However, installing 2.6.2 in Firefox, you can click "Text" which drops down an option for "Whole words". As far as I can tell it's always supported that.

[Michaell]

Don't know about Maestro, but I'm using 0.17.3.

[adoxa]

Doesn't that extension allow you to replace "whole words" only?

Nope, it works on strings inside a word.

I didn't actually test it, but it does at least offer "Whole words" (and RE, which could provide same).

foxreplace-replace-type.png

[Moonchild]

Regexes are very powerful and will easily allow you to include all delimiters if "whole words" isn't working for you.

[Mæstro]

Don't know about Maestro, but I'm using 0.17.3.

I use the same version as you. This version does not offer regular expressions or whole word filters.

[Cassette]

Don't know about Maestro, but I'm using 0.17.3.

I use the same version as you. This version does not offer regular expressions or whole word filters.

It does, though. Look at the image adoxa shared. You click on the T next to the word "Replace" and it gives you the option.

[Mæstro]

It does, though. Look at the image adoxa shared. You click on the T next to the word "Replace" and it gives you the option.

I never realised this. Thank you!