• AdaA
    link
    fedilink
    English
    arrow-up
    3
    ·
    11 months ago

    Because user level blocking isn’t really blocking. It’s just filtering. The bigots can still see the content of people that have blocked their instance, and they can even reply to it. The only person that can’t see it is the user who configured the “block”

    • xigoi@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 months ago

      What exactly is the problem with a bigot replying to you if you don’t see the reply?

      Also, they can see the content even if you defederate, because it’s public.

      • AdaA
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        11 months ago

        I’ve gone in to this in depth elsewhere, but the difference is in the number of drive by bigots encountered, and how easy it is for those drive by bigots to interact.

        So, in an open fediverse, with no defederation, and only user level filtering, drive by bigots will come along and hate on someone. That person will block the bigots instance (after being exposed to their hate), but even after that, the bigots will still be able to interact, and other vulnerable folk will still encounter the bigot dog pile. This is exactly how things work on twitter currently.

        But when you can lock down posts to limit who can see them and defederate from instances that attract bigots, then less bigots will randomly see the content from vulnerable folk in their feeds in the first place, meaning less drive bys and less dogpiling. It doesn’t stop targeted bigotry, and it doesn’t stop dogpiling completely, but it makes it far more manageable.