Jump in the discussion.

No email address required.

https://github.com/LemmyNet/lemmy/issues/622

Hardcoded slur filter :marseylaugh:

If you dont like it, fork it. Stop bothering us about it, we will never fully remove the slur filter.

Racism, sexism, transphobia et al are against the code of conduct and goals of this project. Re-arranging how slurs are filtered, where they're stored, or what should be included is up for discussion, but the existence of a slur filter is not.

Again, your "uncensored" reddit experience already exists: go to voat or gab if you want to use slurs.

it would also be counter-productive: in public spaces there's no appropriate context in which bigoted slurs should be used.

Jump in the discussion.

No email address required.

obstinately insisting on an unpopular feature in your application no matter how poor your argument for it may be

:#marseymanysuchcases:

Jump in the discussion.

No email address required.

>can't say no-no words regardless of context

>No porn

Dead on arrival.

:marseydead:

Jump in the discussion.

No email address required.

The slur filter also caused problems on hexbear cause the cute twinks there wanted to use cute twink (but woke.)

Jump in the discussion.

No email address required.

wasn't lemmy 200% Nazi by their standards?

Jump in the discussion.

No email address required.

Jump in the discussion.

No email address required.

The website hexbear.net (formerly chapo.chat :marseysneed:) uses this. The funny thing is (unless it has changed recently) they forked it to use Node in the backend more cause they couldn’t maintain Rust :marseyxd:. They forked it so much though they never got the true ActivityPub support. I believe one of the required features that they forked over was literally pronoun tags :marseylaugh:

Jump in the discussion.

No email address required.

:#marseyheathcliff:

Snapshots:

Jump in the discussion.

No email address required.



Now playing: Cranky's Theme (DKC).mp3

Link copied to clipboard
Action successful!
Error, please refresh the page and try again.