Opened 9 years ago

Closed 6 years ago

#6290 closed (wontfix)

profanity filter

Reported by: programmerq Owned by: nobody
Component: Contrib apps Version: master
Severity: Keywords: template filter profanity
Cc: Triage Stage: Design decision needed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


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 api.

Attachments (3)

profanepatch.diff (1.9 KB) - added by programmerq 9 years ago.
Initial patch
profanepatch.2.diff (1.1 KB) - added by programmerq 9 years ago.
Initial patch - typo fix
profanedocpatch.diff (702 bytes) - added by programmerq 9 years ago.
Initial doc patch

Download all attachments as: .zip

Change History (9)

comment:1 Changed 9 years ago by SmileyChris

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Design decision needed

Perhaps in the humanize contrib? :)

Not sure it's really core worthy though.

comment:2 Changed 9 years ago by ubernostrum

  • Resolution set to worksforme
  • Status changed from new to closed

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.

comment:3 Changed 9 years ago by SmileyChris

  • Resolution worksforme deleted
  • Status changed from closed to reopened

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

But just using PROFANITIES_LIST is a good idea.

Changed 9 years ago by programmerq

Initial patch

Changed 9 years ago by programmerq

Initial patch - typo fix

Changed 9 years ago by programmerq

Initial doc patch

comment:4 Changed 9 years ago by Alex

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.

comment:5 Changed 7 years ago by 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.

comment:6 Changed 6 years ago by Alex

  • Resolution set to wontfix
  • Status changed from reopened to closed

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.

Note: See TracTickets for help on using tickets.
Back to Top