In this comment my use of the “b” word was overzealously suppressed, silently without telling me. I only discovered it when re-reading my post.

There are THREE #LemmyBug cases here:

  1. when the “b” word is used as a verb, it’s not a slur. And when it’s used as a noun, it’s only a slur if not literally referring to a dog.

  2. my post was tampered with without even telling me. Authors should be informed when their words are manipulated and yet still presented to others as their own words.

  3. The word “removed” cannot simply replace any word. It makes my sentence unreadable. In the very least, the word should be “REDACTED”, and there should be a footnote added that explains /why/ it was redacted.

  • TimLovesTech (AuDHD)(he/him)@badatbeing.social
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    1
    ·
    9 months ago

    I agree with those that say if you cannot live with the filter you should pick a new instance. Part of this whole experiment is that each admin is going to go with defaults they are comfortable with, and as a user you need to be respectful of those, or move on.

    I do you agree with you that REDACTED works better in this case than “removed”, as I always see “removed” as a user action for whatever reason. Even the use of something like FILTERED would immediately alert the user and others that the original word(s) was/were removed and a basic understanding of why (it triggered the slur filter somehow).

    I guess I would also go and change the “slur” filter language to just language filter, as not everyone is going to agree on everything an admin may want to filter being a “slur”, it could be any taboo word in that admins location.

    • soloActivist@links.hackliberty.orgOP
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      9 months ago

      There are bug reports and then there is user support. There’s some confusion because I filed a bug report in a user support community (because there is no bug reporting community).

      Indeed the user support solution is to either request that the admin to change the slur filter config, or change instances. But the purpose of the thread was to report a bug in an in-band way (without interacting with a Microsoft asset [#deleteGithub]).