• @pelespirit@sh.itjust.works
    link
    fedilink
    English
    401 year ago

    Forgive me for repeating this, but I think it’s a great analogy and explains all of our thoughts about it:

    I’ve used this analogy before, but threads is like a huge, 5k passenger cruise ship docking in a small town in Alaska. You don’t have to know ahead of time that the 2 public bathrooms, one at the general store and the other at McDonalds, aren’t going to be enough. You can also forecast the complaining about how everything isn’t really tourist ready. It will suck for everyone. The small museum will be overrun and damaged, the people will be treated like dirt. It’s an easy forecast.

    Here’s the important bit, just because they’ve never been in the cruise line business, doesn’t mean you have to give them a chance to ruin your town.

    • SeedyOne
      link
      fedilink
      English
      191 year ago

      Thank you, someone finally looking big picture. I see a lot of folks talking about things like “it won’t harm Threads” or “the federation is all about inclusiveness and joining together” and those people, while correct on paper, are missing the point.

      Put simply, many instances would prefer not to deal with that unnatural influx, and that is their choice. In fact, the best part of the fediverse is not only that they CAN make that choice it’s that they can UNDO it later if need be. I can’t fault some of these smaller instances for being proactive in protecting themselves when few here really know what goes into running and moderating.

        • @ChunkMcHorkle@lemmy.world
          link
          fedilink
          English
          10
          edit-2
          1 year ago

          Yes. My personal guess is that they want to start Threads as just another Federation instance where people build communities and relationships across instances as they do already, and act like a good Fediverse instance, all friendly and open and free . . . and then once there’s enough popularity and/or cross-traffic they will wall off the Threads portion and monetize access, so you’re forced to either pay up to continue in the parts you like and are invested in, or walk away leaving everything you put into it to Meta and paying users.

          Oh, and they’ll suck up as much Fediverse data as they can too, while they’re at it: anything they have access to will be hoovered up for their commercial use, just as it is now. Federating means that all federated traffic will be propagated to Meta servers in due course, and we all know Meta has zero intention of being bound by any agreements in regard to the data of others, regardless of what platitudes they mouth.

          On a personal level, I don’t give a shit whether lemmy.world federates with Threads, but only because I have already made the decision personally not to participate in ANYTHING Meta, and that includes here on the Fediverse.

          I’m already here because Reddit pulled that same shit, and I walked away then too. I learned my lesson. No way will I knowingly cross that line into personally investing time and attention into what Meta could wall off at any time and monetize without recourse for anyone who does make that mistake.

          And I’d rather they not have my data, but it’s not like I’m in any position to stop or prevent it. Best I can do is stay away from all Meta products, apps, trackers, and cookies.

          TL;DR: People can do what they want with Threads, federate or don’t, participate or don’t, just know that Meta can and will wall it off at any time and expect participants to pay in some way to continue.

        • @Meowoem@sh.itjust.works
          link
          fedilink
          English
          -31 year ago

          I get that you, like me, don’t like capitalist companies but what you’re saying is based on nothing.

          They can’t steal content from here that’s literally not possible, this comment here I’m writing now can not be stolen by anyone ever - and not just in the piracy isn’t stealing way but in the it’s public domain so you already all own it too.

          I use stuff from meta all the time and I didn’t steal it, all the vital open source code they’ve created and which is a fundermental part of stable diffusion and other open source tools is benefiting the community - are they only doing this to kill something?

          I understand the logic that successful capitalist company must be evil because that’s how capitalism works but it’s also a lot more complex, open source isn’t just a wishywashy dream for cheapskate nerds like meit’s a powerful and positive force that can benefit everyone even companies like meta without them needing to kill anyone or anything. Participation isn’t just it’s own moral reward it’s actually got a lot of other benefits too.

          Meta might just want to federate because open source is good.

    • Pxtl
      link
      fedilink
      English
      111 year ago

      See, this is the more reasonable concern. Moderating a fediverse instance is hard, and the flood of posts coming from Threads might be a bad problem. That’s a case where I understand the need to defederate. But on the other hand, that doesn’t feel like a solution that needs to be done proactively - defederating from Threads if/when Threads users become a problem seems perfectly reasonable.

      • @pelespirit@sh.itjust.works
        link
        fedilink
        English
        101 year ago

        Here’s the important bit, just because they’ve never been in the cruise line business, doesn’t mean you have to give them a chance to ruin your town.

    • capital
      link
      fedilink
      English
      0
      edit-2
      1 year ago

      What does that even mean in this context though?

      The federated timeline is ready FULL of shit I don’t care about, have no idea what it is, or can’t read it because it’s another language due to people not being able to set their language correctly.

      The only time I’m going to see threads content is if it is boosted by someone I follow (which I want), contains a hashtag I follow (which I want), or in the federated timeline I already don’t use.

      I don’t see the issue.