I’ve seen a lot of comments suggesting Threads should be pre-emptively defederated by Lemmy/kbin instances if it tries to join us. I’m a bit confused what the problem would be. When Meta does its usual corporate bullshit over at Threads, how would that hurt a user or community based on Lemmy.world? If anything, wouldn’t it give the fediverse a boost if Threads users start discovering communities outside of Meta’s control?

I presume I’m missing something, as you can probably tell I don’t fully understand how Lemmy, Threads or federation all work.

  • Swictor@mander.xyz
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    11
    ·
    1 year ago

    Sound to me like the worst case scenario is that some of the users gained in the debacle is also lost afterwards. Why would the users that joined the fediverse with a purpose leave for threads in the breakup?

    • digehode@lemmy.world
      link
      fedilink
      English
      arrow-up
      28
      ·
      1 year ago

      The EEE strategy would lead to the big corporate entity being the way most people interact. New users would go there instead of other platforms to engage. In time, a lot of the users and content would be on the corporate platform because it’s the one that has the most reach, marketing, etc. so defederation would be a big hit.

      • r00ty@kbin.life
        link
        fedilink
        arrow-up
        10
        ·
        1 year ago

        And you don’t need to look too far to see it now. The majority of people posting on the threadiverse come from lemmy. world and kbin.social. Why? Because they were already the established “big instances” and they went there.

        The average user will just go to wherever is the biggest and that will be threads. And when they have the majority of new take up and most people on the other side have the majority of their contacts inside the threads world, then they don’t need us any more.

        This is just the way a corporation operates. Source: I work at a multinational corporation.

        • jcg@halubilo.social
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          Yeah lemmy.world *already" consists of an order of magnitude more users than the next instance to it. Imagine if the lemmy.world admins had shareholders to please who suddenly start asking “why are you giving away all these ActivityPub activities for free???”

    • IronDonkey@lemmy.world
      link
      fedilink
      English
      arrow-up
      9
      ·
      edit-2
      1 year ago

      I can’t speak for anyone but myself.

      I am not attached to the fediverse. The federated aspect is, to me, interesting from a technical standpoint, but irrelevant to my decision to be here. I’m also not particularly attached to foss principles.

      I came here because I got annoyed at reddit. I’ll continue to poke around here exactly as long as it’s entertaining/informative. That purpose is not contradicted by leaving here for threads (it’d have to be a reddit clone instead of a Twitter clone to pique my interest at all, but leaving that aside).

      So if, over the next few years, more and more of the content that I was interacting with was coming from threads, then threads split off, it’s reasonably likely that I’d want to continue interacting with threads. And if the majority of the stuff I was interested in was on threads, I probably wouldn’t bother coming back here.

      A reasonable reaction to that is “don’t let the door hit you on the way out”, and that’s fine. But what could conceivably happen is that something like threads uses what has been built here to gain ground, then starts leeching away communities. They start moving to Facebook servers because Facebook has butt tons of money so the servers are stable, and besides, everyone else can still get there from other instances. Then Facebook starts adding incompatible features, which motivates more migration to their instances, and so on and so on, then there’s a split.

      Now Facebook’s threads has devoured your communities, taken your users, and so taken your content, mostly just to jumpstart it’s own growth. To get what they are familiar with, people like myself stay on/move to Facebook, leaving the fediverse to rebuild the communities that it built in the first place, out of the people who care more about foss principles. While appearing to external observers like an inferior clone off the Facebook threads thing, to add insult to injury.

      So the issue is that you wouldn’t lose just the new stuff from Facebook, but a fair bit of the preexisting stuff that sided with Facebook after the split out of convenience. What you’d keep are the people who stick it out out of loyalty to foss or federated or some other principle - and that may not be enough to carry on the level of content that’s desired, even with the fediverse’s “size isn’t everything” philosophy.

      Of course, it’s possible that either a) none of that would happen even if there were federation with Facebook and everything would be fine forever, or b) all of that would happen even without federation with Facebook, just without the intermediate stage where there’s interaction. But the above seems to be the concern, and it’s not without merit (both because of past examples and, well, because I know I personally wouldn’t stay if the content were more appealing somewhere else and I don’t think I’m unique).

      Personally, I think that with Twitter reeling at the moment, all the Facebook version has to do is be similar enough to be familiar, have good performance, and be easy to use to have a shot at that nabbing that part of the market (including users from the fediverse) - interoperability with mastodon or not. But predicting the future is rather difficult, so it’s hard to say.

    • GunnarRunnar@kbin.social
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      There’s also users that potentially could joined other instances but because of some exclusive feature Threads has, they choose it. So basically rest of the instances are bleeding users to Threads.