• @simple
    link
    1272 years ago

    I’m for blocking Threads. I’m not for blocking instances that support Threads. That’s ridiculous, you’d just split the community and make the Fediverse irrelevant.

    • @Protegee9850
      link
      02 years ago

      The fediverse wasn’t irrelevant yesterday and it won’t be if it defederates Meta proactively before they have the opportunity to ruin the ecosystem.

      • @simple
        link
        7
        edit-2
        2 years ago

        If you defederate with non-meta instances you’re going to vastly reduce local content and encourage people to give up and go somewhere else. What good would that do? Like I said I’m for defederating with Threads, but attacking everyone that doesn’t is a waste of effort and is going to ruin the community.

        • @Protegee9850
          link
          -12 years ago

          Due to the architecture of the fediverse instances federated with Meta give them access to the data of those on those instances, even if they’re not meta owned. Defederate on is afaik the only way to stem that flow.

          • @simple
            link
            3
            edit-2
            2 years ago

            That’s not the danger. It’s super easy to gather data on the Fediverse, I can just self-host an instance and connect with everyone and scrape the internet and all that.

            The danger, from my pov, is that people would be so dependent on major companies that they can hold a power position over the Fediverse. If 90% of people on your instance use Threads, and Threads decides to defederate or slowly creep in proprietary features you’re not allowed to use, people would feel like they’re being forced to make an account there or leave smaller instances. That’s the EEE scenario, I don’t think privacy (from our end) is a huge concern right now.