profanity filter

[Jeff Anderson]

A feature that would live somewhere in contrib--
It would contain a template filter that replaces profanity with * or @!%#$(#!
It would be easy to write, and it could be configured to use either a static list, or use the webpurify.com api.

[Chris Beaven]

Perhaps in the humanize contrib? :)

Not sure it's really core worthy though.

[James Bennett]

django.core.validators (part of the oldforms system) already contains a hasNoProfanities validator which uses the setting ​PROFANITIES_LIST and throws a validation error. I imagine something similar will be available eventually for newforms, though I'm not sure where exactly it will live.

[Chris Beaven]

A profanity validator and a profanity filter aren't exactly the same things.

But just using PROFANITIES_LIST is a good idea.

[Jeff Anderson]

Initial patch

[Jeff Anderson]

Initial patch - typo fix

[Jeff Anderson]

Initial doc patch

[Alex Gaynor]

I would say if we want to really offer this we should probably fix the profanity list, which isn't even remotely all encompassing, or even looks like a real attempt at such.

[Thejaswi Puthraya]

I doubt if we should go ahead especially with the reluctance of the BDFLs
(see #8794).

Maintaining profanities like Alex mentioned would be very difficult. Just
take into account the large number, then i18n variants and finally the
number of tickets people might open to add new ones.

[Alex Gaynor]

the profanities list has been on the chopping block for a while, and this is actually a non-trivial problem not fit for django core, wontfixing.