Integrate with badwords https://github.com/hughsie/badwords

[dcampbell24]

Motivation

I think the OARS guidelines follow this list.

Summary

Integrate with badwords. Have the option of choosing OARS bad words and mild, moderate, or intense. This should be in addition to exiting filtering.

Alternatives

I can't think of any.

Context

NA

[dcampbell24]

badwords is licensed under the LGPL-2.1, so if you are going to include the list of words from that source in your source, you will have to keep it as its own file and note that that file is licensed under the LGPL-2.1.

[dcampbell24]

You can add a note in the README.md you could also make the project REUSE compliant: https://reuse.software/faq/#uncommentable-file. It's not too much effort, makes the licenses of all the files explicit, and there would be no way upstream could complain (I think??).

[finnbear]

Hi, thanks, I will not be including the list in rustrict, or making it a separate category of profanity in the API, but I may use it to fix gaps in profanity.csv.

[dcampbell24]

Because the OARS filtering is much simpler than yours, I made a basic package to do the filtering.

[dcampbell24]

Just an FYI, you can't include any content from looking at badwords.csv without making your license LGPL-2.1-or-later... Maybe you should just close this issue.

(I am not a lawyer, but I am pretty sure that is how it works.)

[finnbear]

I'm aware of how licenses work, but licenses only protect copyrightable content. Individual profanities are not copyrightable and, for lists to be copyrightable, a necessary condition is that the selection/arrangement is creative. A list's selection isn't creative if it's intended to be an exhaustive list of words in a particular category (single-word profanity in a particular language). A list's arrangement isn't creative if it is lexicographical ordered. For example, the list section of a phonebook is likely not copyrightable. Definitions of each profanity are likely copyrightable but I wouldn't use those. If I use many profanities from this repository, I'd acknowledge it, e.g. in my README, but not change my license.