I just got permanently banned from a community for making a single harmless remark on a single post that was right there in the main feed. It’s not a community I’m super active in so it’s not like devastating, but it is annoying

If your precious little community is full of so many delicate sensitive people who can’t even be reminded that another viewpoint even exists, then you should really protect them by defederating and having everyone join your private website

The mod has literally removed like 75% of the comments and banned everyone lol

I don’t know about anyone else, but I don’t have time to read every rule for every community that pops up when I’m in view all

  • Admiral Patrick@lemmy.worldMEnglish
    0·
    3 months ago

    Also, what’s up with not being able to block a community you’re banned from?

    Wait, really? I’m gonna have to check on that. Curious if that’s an API limitation or a frontend bug. What frontend did you use? Lemmy-UI?

    • dual_sport_dork 🐧🗡️@lemmy.worldEnglish
      0·
      3 months ago

      I just checked and using the default Lemmy UI (on desktop) you totally can block communities you’re banned from. I’m pretty sure what we’re looking at must be some kind of UI/front end bug.

      • Admiral Patrick@lemmy.worldMEnglish
        0·
        3 months ago

        Thanks for the additional info. I’m gonna set up test cases in the UI I work with and try to confirm (and handle it better if need be). A UI bug was my assumption as well.

      • Admiral Patrick@lemmy.worldMEnglish
        0·
        3 months ago

        Thanks. I’ll add that to my test cases for the UI I work with. I don’t think I’ve ever tried to block a community the test user was banned from, so I’m curious if it’s an API restriction or the way the UI handles it. Will prob also submit a bug once I figure out which.

        Edit: That looks like the community options that have the “block community” button are all hidden when you’re banned rather than the “block” functionality being restricted. I’m almost positive now that it’s just a UI bug. Will still add it to my test cases, though.