• tal@lemmy.today
    link
    fedilink
    English
    arrow-up
    9
    ·
    edit-2
    8 months ago

    I agree 100%. I don’t need someone else overriding my existing right to decide whether I want to block or not (where is that going to stop).

    To some extent, most instances already do that on some instances, whether they do it for Threads or not.

    So, you’re @danie10@lemmy.ml.

    Your home instance is lemmy.ml. Its federation list is at:

    https://lemmy.ml/instances

    It includes in its Blocked Instances list, has defederated with, 181 instances.

    Now, you might well agree with some of those being blocked. Like, maybe they’re spammers or harassing people or God knows what. They might host speech that might be illegal in some jurisdictions, be classified as hate speech there. They might contain content that’s socially-unacceptable in some countries – one of my first experiences on the Threadiverse was being sent by a random kbin.social sidebar comment recommendation into a conversation that Ada, the lemmy.blahaj.zone instance admin, was having with some guy in the Middle East, whose country had apparently blocked that instance at the national firewall level due to it having LGBT content or something like that. There’s pornography on lemmynsfw.com. Consentual-nonconsentual and synthetic child pornography on burggit.moe. Piracy material on lemmy.dbzer0.com. Some instances won’t approve of that being accessible from their instances, and in those cases, the instance admin is already blocking things.

    I chose my home instance – lemmy.today – specifically because it was an instance policy to try to avoid defederating with instances, and it presently has an empty blocklist. But as best I can tell, most instances have some level of content or user behavior or whatever on other instances that they consider unacceptable and will defederate over. Maybe not it’s not Threads, but they’re aiming to block something.

    • GadgeteerZA@lemmy.ml
      link
      fedilink
      English
      arrow-up
      5
      ·
      8 months ago

      Good points. Yes, I do prefer to give an instance at least the benefit of the doubt. Difference tho really with Fediverse is you have to search and follow stuff to see it. It does not get inserted into your feed through ads or people playing the algorithms. So generally I’m only seeing what I follow. I suppose we do need to choose our instances wisely. Certainly, if an instance (not just a user on it) is really spamming or impacting on other instances, I suppose there can be grounds to block it. But we have not all been spammed yet by Threads. I don’t like Threads (cancelled all my accounts years ago) but I left a few good friends and family there that I would like to reconnect with, and follow them. I also like that my metadata stays on the Fediverse side, so I don’t need a Threads account or their app tracking me.

      I just would not like to be denied the option to even reconnect with my family and friends. Same goes for WhatsApp interoperating on Signal protocol - I have many friends and colleagues I left behind on WhatsApp, and would like to reconnect again with them.