On principle, I would say that I do personally object to profanity in posts and signatures in general, but I've become pretty good at just ignoring isolated bits, and if the post is too thick with them, I don't read them. I'd rather not have to see the profanity, but that's the world we live in.

Given Perlmonks partial identity as a place for newbies to ask for help, we should probably avoid profanity as much as possible, but I think that a -- vote for particularly offensive nodes or a /msg to the offending monk is probably a much better response than trying to filter things automatically. Besides, He Who Must Not Be Named must have better things to do with his time than to axe four-letter words.

So, I guess I'm basically concurring with the rest... The "solution" here would have been to discuss this privately with PodMaster. Since he seems to be "intransigent" on the issue (see his response), though, I suppose even by that logic, coming public with the discussion was the right thing to do. But it seems that you (and I) are in the minority here.

Perhaps you, princepawn could produce the necessary hacks to invoke your module based on a user preference. Based on vroom's comment on the original node, I don't particularly want to read the docs for your module to do it myself. :-) I doubt that Our Fearless Leader would object to a drop-in solution that makes a long-standing monk more comfortable in the monastery without incoveniencing the others. (Of course we then would have to have the discussion as to whether this defaults to "on" or "off"...)