#Fedipact - The instances blocking Zuckerberg's Threads.net
fedipact.veganism.social
An interactive list to see which ActivityPub (Matodon, Lemmy, FireFish, etc) instances are federating with Threads.net
  • fruitycoder@sh.itjust.works
    2618·
    11 months ago

    I still stand by that defederation as the only line of defense is a losing strategy. Keeping users siloed in Facebook’s garden shouldn’t be seen as a win for us.

    • Olgratin_Magmatoe@startrek.website
      712·
      11 months ago

      Keeping users siloed in Facebook’s garden shouldn’t be seen as a win for us.

      Sometimes the only winning move is not to play. If people hadn’t federated with google’s XMPP back in the day, google wouldn’t have had the same level of control it had to kill XMPP as a competitor.

      We need to learn from the lessons of the past, and the past has resulted in the deaths of services when federating with corporations.

      • Fox Trenton@lemmy.ml
        112·
        11 months ago

        “We should debate them… And defeat them on the Marketplace of Ideas.” Yeah, right.

        • Olgratin_Magmatoe@startrek.website
          71·
          11 months ago

          I never said defeating them or out competing them should be the goal. The goal should be the survival of services. And corporations will kill these services.

      • Flaky@iusearchlinux.fyiEnglish
        618·
        11 months ago

        Hate to burst your bubble, but no-one was actually using XMPP with Google Talk except for open-source tech nerds.

        • Alsephina@lemmy.ml
          152·
          11 months ago

          And google stopped any chances of that ever happening. The Fediverse should just let itself grow gradually and naturally, as should have XMPP

            • poVoq@slrpnk.net
              51·
              11 months ago

              They piggy backed on rapidly growing XMPP and then became lazy with keeping compatible with the rest of the xmpp federation and at some point the s2s connection stopped being feasible as they never implemented TLS for it, and did’t really care as most xmpp users were on their server anyways and thus did’t use the s2s connection.

              Its not a typical nefarious EEE story, but it did a lot of damage to the xmpp federation anyways.

        • poVoq@slrpnk.net
          51·
          11 months ago

          This predates Google Talk and is rather about the XMPP Gmail integration. Back then XMPP was the hot topic in tech circles (Twitter was even prototyped to be XMPP based) and people were switching to it and recommending it to others to replace ICQ/MSN/AIM etc. However, often they recommended others to use the Google XMPP service as back then Google was still naively seen as the “Do no evil” good guy, having just started up recently and giving away free things like previously unheared off 1GB of email storage etc.

          So the situation is not quite comparable to AP and Facebook (and XMPP is far from dead), but it is still possible to draw some lessons from it.

      • fruitycoder@sh.itjust.works
        3·
        11 months ago

        The most free people. Best for society. Etc.

        |They’re welcome to come here whenever they like .

        Only if they know it exists and can still connect with the people and communities they care about. This is what the federated approach was supposed to fix, the silos, the community capture.