https://en.wikipedia.org/wiki/S****horpe_problem
>Wikipedia actually has a redirect for that
>lol

I tried (and failed) to test whether this worked in my previous thread here with a certain word, but forgot that it wasn't even in the wordfilter.

Either way, perhaps it would be better to move the wordfilter code into the post renderer (after things like BBCode are parsed), rather than it being part of the thread/post submission? That could also allow for doing more flexible filtering, perhaps using regexes and stuff like that.

Having it operating on URLs and unrelated partial words isn't really a great idea unless one intentionally meant to do so.

This also relates to matching on leading spaces or not, which is already adjustable. From my perspective it's up to the admins to configure as desired based on translation and community standards.

https://m.youtube.com/watch?v=****-5yGrk

a better example of what I'm trying to illustrate can be seen with this URL, I suppose - which doesn't even censor properly as the word that's there is 5 letters, and it censors it to four stars...

(I'd personally only use wordfilters for the sort of things you'd see back on oldschool 4chan anyway, that or for creating "hidden" smilies, but it seems like you could break thread titles by doing the latter... also, not sure if the filter retroactively applies to existing content)

We don't have any 5-char censor substitutions that would explain what you're talking about, so I really don't understand your point about the broken URL.

The word in question can mean "female dog". Should be a hint.

That said, the actual URL posted changes to the four stars and this means the video can't be posted (which, rather amusingly, relates to a facebook group about dogs...)

I'm still confused about this address. When I substitute the b-word for the 4 stars it still appears to be an invalid address on YouTube. Are we talking about a hypothetical issue with link processing or is there a reasonable test case that shows something isn't working as expected?

The B and the T are capitalised in the URL. YouTube video IDs are case sensitive.

And yeah, I was trying to illustrate a hypothetical situation where a posted link fails because of the filter, however simply changing the word

This also breaks hotlinking to and/or fetching images that have expletives in them.

The fact I can bypass the filter by simply putting a blank BBCode tag in the middle of a word also defeats the purpose.

By the way, the one for shite doesn't even work properly, since it censors shit before anyways.

Perhaps this part of the code needs reworking a bit more thoroughly (and also, the default settings for this are... not great to say the least. I can think of a lot more ones to add, mostly slurs, and was even going to put a commit in - but I then thought to myself: "these words might mean something in another language", and also the fact that I clearly only wanted to do that just to have an excuse to submit a commit with a bunch of funny words in it.

(To be completely fair though I didn't even realise it censored words by default until I wrote a censored word, IIRC. I just never thought to check that part of the admin panel, assuming it was empty.)

Pretty much any place name that is amusing to Anglophone tourists probably falls under such circumstances.