Corporations don’t just sit out on new technologies, and no matter how hard you try you can’t force them to. Defederating from Meta’s new project preemptively is naive, and will not do much of anything.

Protocols are going to be adopted by corporations, whether we like it or not. SMTP, LDAP, HTTP, IP and 802.11 are all examples of that. If it ends up that meta is able to destroy the fediverse simply by joining it, that is a design flaw on OUR end. Something would then clearly need to be different in order to prevent future abuse of the protocol.

FOSS is propped up by corporations. By for profit corporations. If you want to stop those corporations from killing projects, you put safety guards up to make sure that doesn’t happen. You don’t just shut them out and put your head in the sand.

  • femboy_link.mp4@beehaw.org
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    1 year ago

    If it ends up that meta is able to destroy the fediverse simply by joining it, that is a design flaw on OUR end.

    “Simply by joining it” is not an accurate representation of what will happen in the slightest. Meta is not some scrappy little Lemmy instance operator relying on donations to keep the lights on, they’re one of the biggest companies in the world who simply do not care about fair competition or open standards, and they have a proven track record of using that position to either buy out or destroy competition.

    When Meta have so much money that they can simply outspend any other fediverse platform and become dominant that way, how is that a design flaw on our end? You can make a project as resistant to corporate overreach as you like, infrastructure to run it still costs money and there is no fediverse operator on the face of the earth that is going to be able to outspend Meta when it comes to infrastructure and R&D. How is defederation not an appropriate response when smaller instances are crippled under the inevitable load stemming from Metas users?

    Corporations have been embracing, extending and extinguishing FOSS projects in the tech space for decades now, and their demise has rarely been because of a fatal flaw in the projects themselves. It’s been an intentional play by Microsoft, Google et al to ensure that there is no viable open alternative to their walled gardens. Trusting them in any capacity is naïve at best and catastrophic at worst.

    I encourage you to read this blog post which outlines these concerns much better than I can: https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html

    • ryan@the.coolest.zone
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      When this was linked a previous time, I wrote up a reply to it which I think applies here as well, so I’m gonna shamelessly copy and paste myself 🙂

      I think the big thing to take away from that article is… XMPP developers cared so much about retaining federation with Google Talk that they “became watchers and debuggers of Google’s servers” as it is put there. Google came in and said “this is our house now, adapt or die.”

      For our current fediverse, it’s important I think, as a community, we put our foot down with Meta and say “no, this is our house. If you don’t adapt to us, we don’t federate with you. If you deviate from the ActivityPub protocol or our other implementations that we do above the ActivityPub protocol (things like boosts/upvotes/downvotes standards as agreed upon by Lemmy/kbin, for example), you will break federation with us, and we will be okay with that.” We cannot become the Meta watchers.

      ActivityPub is just a protocol and they can use it. It doesn’t mean they have to be compatible with us. Let them have their Twitter/Instagram hybrid application. Do we care that much whether we can or cannot see their posts?

      To your point, many of us will defederate, either out of politics or financial necessity. There’s rumors milling around that Meta / Threads will only initially federate with a few trusted larger instances and be monetarily compensated for it (aka those who will make a deal with the devil to moderate - more on my thoughts on that here).

      It may come to the point where a lot of us are running on our own smaller “Fediverse”, intentionally divorced from Meta and those instances which have federated with Meta and taken their advertisements and paid posts. If this is the case, we must take the bad with the good - we will always be smaller and niche, and our less techno-idealistic friends will not join our tiny Fediverse because the barrier to entry will remain high.

      • Spzi@lemm.ee
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        as a community, we put our foot down with Meta and say “no, this is our house. If you don’t adapt to us, we don’t federate with you. If you deviate from the ActivityPub protocol or our other implementations that we do above the ActivityPub protocol (things like boosts/upvotes/downvotes standards as agreed upon by Lemmy/kbin, for example), you will break federation with us, and we will be okay with that.”

        I’m afraid we will lose if we accept them until they do something bad. Given their track record, that’s just a matter of time. If we let them become important to the fediverse as long as they play nice, the final decision could be disastrous for the fediverse when they stop playing nice.

        So the right thing to say seems for me: “No, this is our house. We don’t federate with you.”

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

        It will follow the EEE flow along with their normal anti-competition tactics. First, they embrace: their interest in federation is only to give them the access to content that will make their platform not look empty, allowing them to put their coffers to work on drawing the majority share of users. Then they will extend: they will make sure their platform is compatible with ingesting other server content but others will be unable to federate their content (they will become “incompatible” later, due to “features”). Then they will extinguish competition: they’ll cut off what little engagement is left with those (inbound only) federated servers because they no longer need them and the majority of the remaining users will move to their platform because that is where the activity is.

        Then Kbin/lemmy will be just like all the other random phpbb instances that no one really uses. Being naive won’t make things any less likely, yet there will always be gullible people who argue that “of course they will embrace the technology” and that everything else is just non-sense/wouldn’t have worked anyway/blah.

        It doesn’t take long for the largest servers to have operating costs that they will happily allow Meta to burden in exchange for nearly any concession. The main problem is that, while Kbin/Lemmy is federated, it is federated in a manner that still places content in silos and allows single servers to “own” those spaces. It hasn’t really fixed the problem yet, it just spreads the problem out over a few more servers. Until spaces are universal (every server owns a slice of that community, spreading out the community instead of just the users), it will remain ripe for EEE.