Hey, I just did a quick browse through the blocked instances list for infosec.pub and have a few questions about it. Seems like we are blocking sh.itjust.works which at first glance just looks like one of the bigger general purpose instances. Meanwhile more overtly problematic instances like lemmygrad (tankie instance) or exploding heads (“free speech extremists”) are federated with. Generally the block list seems fairly small compared to a lot of other instances.

So are these intentional choices or is it more a matter of the admins not (having the time to be) bothering with it? If it’s not intentional, maybe checking some other instances blocklists to weed out the biggest trolls/offenders could be useful.

  • CoderKat@lemm.ee
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    2
    ·
    1 year ago

    IMO it’s not a good solution to just say “just block the bigots”. The problem is that for new users, they are going to see those bigoted posts. They’re going to either think that’s what kind of site Lemmy is and potentially leave, or they’ll potentially get pulled in by the bigots. Both are bad situations.

    Especially for blatant bigotry, it makes perfect sense to take measures to ensure that the site is safe for everyone by default, without every individual person having to take action (especially those without accounts or not signed in).

    • mwguy@infosec.pub
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      1 year ago

      So lemmy needs a “soft” block. A system that moderates it out of the default streams, but allows an individual user to still add communities they want to see in their subscriptions.