From the README: Profanivore is a Bugzilla extension which 'eats' English profanities in comments, leaving behind instead a trail of droppings ('****'). It finds its food using a standard library Perl regexp. The profanity is only eaten where the comment was written by a user who does not have the global 'editbugs' privilege. The digestion happens at display time, so the comment in the database is unaltered. However, it does not eat profanities when showing people their own comments; the aim here is to prevent people immediately noticing they are being censored, and getting 'creative'. The purpose of Profanivore is to make it a little harder for trolls to vandalise public Bugzilla installations. It does not currently affect fields other than comments. I wrote this very carefully to walk the line between being over-censorious and being protective of our users having to read abuse from trolls. Hence the "you can swear if you have editbugs" feature. The code currently is only on my hard disk (it's very simple) but I can put it in the extensions repo. Do people on the CC list think this would be a reasonable change? If so, I can open it up for wider discussion in a newsgroup. Gerv

http://bzr.mozilla.org/bugzilla/extensions/profanivore/trunk/files A little more background: this was inspired by a request from nmiller in a bug about the recent b.m.o. troll, idrugoy. Gerv

$comment->author->id ne Bugzilla->user->id The IDs are numerics, no? So, '!=' instead of 'ne' would be better there.

Seems low impact and useful for BMO IMO. If enough people complained, it could be pulled if need be. There will always be some that claim freedom of speech infringement, but when it comes to obscenity, privately held websites should be able to initiate any measures they feel appropriate. Dave

I think an interesting configuration option would be the ability to force this control only on accounts that are younger than X weeks (e.g. account created 2 weeks ago vs 2 years ago). The thinking is that many spam comments originate from accounts that are specifically created for a spam rampage and then eventually caught and deleted by an admin. By only enforcing this filter on young accounts we can defeat the spammers and have no change to more established (and hopefully) trusted users. This is just an idea, if we want this plugin for all users then that's good with me too.

(In reply to comment #4) > I think an interesting configuration option would be the ability to force this > control only on accounts that are younger than X weeks (e.g. account created 2 > weeks ago vs 2 years ago). People might then just create accounts and come back later :-) Surely it's much better and easier to bind it in to Bugzilla's existing permissions system. Accounts created for spamming are not going to be given editbugs. Gerv

Unless anyone CCed on this bug objects quickly, I plan to blog and newsgroup-post about this plan this week. Assuming we still want to go ahead after that, I'll check it in to the 4.0 and 3.6 repos. Gerv

OK, no significant objections, so let's ship this. Committing to: bzr+ssh://gerv%40mozilla.org@bzr.mozilla.org/bmo/3.6/ added extensions/Profanivore added extensions/Profanivore/Config.pm added extensions/Profanivore/Extension.pm added extensions/Profanivore/README Committed revision 7244. Committing to: bzr+ssh://bzr.mozilla.org/bmo/4.0/ added extensions/Profanivore modified extensions/BMO/Extension.pm added extensions/Profanivore/Config.pm added extensions/Profanivore/Extension.pm added extensions/Profanivore/README Committed revision 7508. Gerv

For the record, this adds an additional RPM prereq for the webheads. I've added perl-Regexp-Common to the package list for the production webheads in the puppet config and installed it on mradm02 so we don't blow up Bugzilla when this gets pushed to production. :)

Well spotted. Thank you :-) Gerv

Fuck

Verified that this works as intended for accounts with proper permissions :-)