Server indexes of places for newcomers to join can be instrumental for Fediverse adoption. However, sudden rule changes can leave some admins feeling pressure to change policies in order to remain listed.

  • Maybe I’m naive but I kinda don’t get it. People talk about defederating as if…what, all Meta IP addresses will be magically blocked from scraping your content? Any script kiddie can harvest Lemmy/Mastodon/whatever content.

    Has Meta shown itself to be a bad actor? Yes. Should my email provider block all emails from Meta? Well…that’s a bit much I think? If Facebook email still existed, should my email provider block that?

    My point is yes, Meta bad, but all Thread users also bad? I thought — and apparently I’m very wrong here — that the Federation paradigm was kinda like email. And the only email I want blocked is a domain where every single user is malicious, not a domain run by a malicious entity which has normal people as users, who aren’t necessarily very tech literate.

    I don’t actually care, but I just find it a little confusing tbh.

    • @qjkxbmwvz I think the main fear is Embrace Extend Extinguish.

      It’s not about interacting with Threadworms, it’s about sleepwalking into a situation where Meta is changing the very nature of ActivityPub itself.

      • I’m actually curious about “Embrace Extend Extinguish”: What can they do? They “extend” the ActivityPub protocol in a proprietary way, ok. Doesn’t mean any other instance has to use that, no? Ok, that would mean if an instance doesn’t follow that extension, it can’t interact optimally with Threads, but how does it matter? To me it seems all that can be lost by that is the content/user base that Threads brings into the Fediverse and then we are at the same point as we would be if we defederated immediately. Maybe I’m missing something here?

          • I guess it is impossible to say what would have happened if Google never used XMPP. To me it mostly looks like google joined XMPP and made it way bigger than it was before and eventually left it again, making it small again. But is it worse than before Google even joined?

            Maybe, but can we say for sure?

            Maybe the lesson is not “don’t let the big corporate players in”, but rather “make sure the development of the underlying protocol itself is done in an open way”. If Google/Meta adds proprietary extensions, just don’t add them to the main protocol. If they leave the protocol again or changed their implementation in a way that is largely incompatible with the open version, nothing is lost than what they brought in initially. Doesn’t that make sense?

            • I agree.

              I think a good example is how Slack started off by having good IRC integration, then slowly added features which were incompatible with IRC, and finally terminated IRC integration.

              So clearly, Slack killed IRC, right? (…of course they didn’t!)

              I see the potential situation with Threads as similar.

              • the problem occurs when most of the content comes from Meta (they will likely have the vast majority of Fediverse users). especially if major communities exist on their instance. when meta decides to no longer support fedi integration, those in the fedi are forced to decide between staying with their communities by ditching the fedi and moving to threads or having many of their communities ripped away.

                meta will do this at some point as a play to draw users to them, but we can decide if we want to be affected when that comes to pass.

    • I dont care if they scrape my comments I just wouldnt want to see sneaky “promoted” posts aka ads and I enjoy the idea of boycotting facebook.

      Ultimately the decision is for the instances owners and admins to make, not ours. I will just migrate to one that doesnt federate with facebook if I have to.

      • I just wouldnt want to see sneaky “promoted” posts aka ads

        I don’t quite see how that would even work. Those posts would need to be coming from individual users rather than from Facebook itself and you can just block those users. Facebook can display ads in between posts on their own app but those wont be visible to people using other apps.

        •  grrgyle   ( @grrgyle@slrpnk.net ) 
          link
          fedilink
          7
          edit-2
          7 months ago

          Here’s one scenario.

          1. Facebook feeds its users content according to an algorithm.

          2. Facebook and lemmy users can interact with the same user content (liking, commenting).

          3. There are vastly more Facebook users than lemmy users.

          4. By dint of Facebook’s greater number of users, lemmy users will see the most popular content that is fed algorithmically to Facebook users.

          Conclusion: lemmy users are being fed content by the Facebook algorithm (in this still, thankfully hypothetical, scenario).

          Like imagine Facebook promotes some viral post and it gets a thousands of upvotes. Any lemmy user on a federated instance, sorting by upvotes/hot/etc, is going to see that post.

          That’s the kind of top-down reach that is so alien to the fedi

    •  Otter   ( @otter@lemmy.ca ) 
      link
      fedilink
      English
      107 months ago

      I agree, and I predict people will eventually pick instances that are doing what you suggested.

      My understanding is that the defederation is to prevent MetaFacebook from getting to a point where they control the entire thing and then destroy it.

      I don’t think defederating is the right move for that, but it’s a move

    • And the only email I want blocked is a domain where every single user is malicious, not a domain run by a malicious entity which has normal people as users, who aren’t necessarily very tech literate.

      You’ll never get the tech iliterate people to switch to the rest of the Fediverse otherwise. Defederating Threads is about making it as bad as possible for its users - it’s about hurting Meta and stemming its bad influence on the web.

    • I think most people simply just don’t know how federation works and they imagine that defederating blocks Facebook from accessing your content when in reality it’s the exact opposite; it places one way mirror between us from which only they can see thru. There’s also some great irony in the fact that they’re talking about genocide while advocating for using the nuclear option to block Facebook despite the massive number of innocent casualties it’ll cause.

      EDIT: Turns out I was mistaken. Defederation indeed does stop the flow of data both ways.

      • it places one way mirror between us from which only they can see thru

        What do you mean by this? Even if Meta would collect data from defederated servers (I don’t think they would), it would be massively more complicated than if they were federated.

        • Federarting means there’s a two-way road between your instance and threads.net and traffic can flow both ways. When you defederate it stops the traffic flow from threads.net to you but the traffic from you to them is unchanged. Even if every single instance defederates them they can still see all the content that’s posted there. Nobody else just wont see any of theirs. Only your instance admins know your email, ip-address and so on but all your posts and messages are publicly available to anyone and you can’t stop them from accessing it.

          It’s basically the same thing as blocking an user. You wont no longer see their messages but they will see yours.

          EDIT: Turns out I was mistaken. Defederation indeed does stop the flow of data both ways.

          • When you defederate it stops the traffic flow from threads.net to you but the traffic from you to them is unchanged.

            No, that is not how defederation works. One server defederates, traffic stops in both directions. It’s not comparable to user blocking.

            posts and messages are publicly available to anyone

            There’s a big difference between the posts being available publicly on the Web and them being sent to Threads via federation.

      •  livus   ( @livus@kbin.social ) 
        link
        fedilink
        1
        edit-2
        7 months ago

        There’s also some great irony in the fact that they’re talking about genocide while advocating for using the nuclear option to block Facebook despite the massive number of innocent casualties it’ll cause.

        Sir/Madame, not being able to see some online content is nothing at all like having your family members murdered in real life.

        Read A Death Sentence For My Father sometime and you will see.