I realize that Phabricator is not the best place for discussion and debate, but I also feel it's useful to respond to comments by @DCDuring in this context.

Responding to comments by @DCDuring:

@CBogen Thank you. I had a feeling this would be acknowledged as an issue that should be fixed once the right people saw it. @Aklapper I have renamed this again. The key word is "are offensive" as defined by Wiktionary itself.

@Aklapper Thanks for the rename. Definitely better, but not quite right though.

@Aklapper OK, let me also be clearer. First, I renamed the task to make it clearer I'm not suggesting that offensive words not be included in the corpus. Second ...

@Aklapper You are pointing to an article that I have already read (many years before I submitted this bug report) and that you and @DannyS712 are misinterpreting. You're also both misreading what I wrote, which is disappointing and a bit sad. I am not suggesting censorship. I am stating that autocomplete returning racist and offensive results is actually in violation of Wikimedia policies (as I cited), and that it should be fixed.

I am reopening this because @DannyS712 has misunderstood it. I am very aware of Wikimedia rules about censorship and I am not suggesting that Wiktionary be censored. Of course, offensive words need to be here in order to document their offensiveness. But, if you take the argument that "Wikimedia projects are not censored" too literally, then the page for the N-word should merely say "a Black person" and should not mention that it is offensive, vulgar, or a slur. Those (accurate) descriptions are far closer to censoring than fixing this bug would be. Yet they are needed to properly define and document the word.