Part 3 of Strategies for the free fediverses

cross-posted from: https://lemmy.blahaj.zone/post/7193618

The “free fediverses” are regions of the fediverse that reject Meta and surveillance capitalism. This post is part of a series looking at strategies to position the free fediverses as an alternative to Threads and “Meta’s fediverses”.

      • The Nexus of Privacy@lemmy.blahaj.zoneOPEnglish
        91·
        9 months ago

        You do realize that instances federating with Threads will share data with Threads, and that Meta’s supplemental privacy policy specifically says that they’ll use all activity that federates to meta for tracking and ad targeting, right?

        So for example, if you’re on an instance that federates with Threads, and somebody on Threads is following you, all of your posts – including your followers-only posts – will get tracked by Meta. Or if somebody who boosts your post and they’ve got followers on Threads, your post will be tracked by Meta. Or if you like, boost, or reply to a post that originated on Threads, it gets tracked my Meta. And these are just the most obvious cases. What about if somebody on an instance that’s not Threads replies to a Threads post, and you reply to the reply? It depends on the how the various software implements replies – ActivityPub allows different possibilities here. And there are plenty of other potential data flows to Meta as well.

        Of course they’re still just at the early stages of federation so it’s hard to know just how it’ll work out. Individually blocking Threads might well provide a lot of protection. But in general, instances which federate with Meta will almost certainly be tracked significantly more than instances that don’t.

          • The Nexus of Privacy@lemmy.blahaj.zoneOPEnglish
            2·
            9 months ago

            𝕯𝖎𝖕𝖘𝖍𝖎𝖙: If those instances choose to share data with Threads, you should not join those instances.

            Also 𝕯𝖎𝖕𝖘𝖍𝖎𝖙: Federating with threads shares “data” in the form of content

            I appreciate all the time and energy you’re putting into the comments here, but what it comes down to is that you’re not concerned about the difference between the federation scenario – where this data is given to Threads under an agreement that explicitly consents to giving Meta the right to use the data for virtually whatever they want – and the situation today – where Meta and others can do the work to non-consensually scrape public data on sites that don’t put up barriers.

            We’re not going to convince each other, and we’ve both got enough walls of text up that at this point neither of us are going to convince people reading the thread who aren’t already convinced, so let’s save ourselves the time and energy and leave it here.

              • The Nexus of Privacy@lemmy.blahaj.zoneOPEnglish
                2·
                9 months ago

                Yes, you described what you see as the difference between data and “data” clearly. And I described what I see as the implications clearly. If anybody’s still reading the thread, they can make their own conclusions.

                It’s less of an agreement and more of a protocol.

                Threads Supplemental Privacy Policy begs to differ that there’s not an agreement here.

                My point is that defederating from meta doesn’t stop meta from tracking you online.

                I never claimed it did. It eliminates one path of consensually sharing data (or “data”, in your terms) with Meta.

                In terms of your list, my perspective is that a server that federates with Threads is part of Meta’s ecosystem – #1 in your list. You don’t seem to see it that way, and that’s what we’re not going to convince each other about.

                  • The Nexus of Privacy@lemmy.blahaj.zoneOPEnglish
                    1·
                    9 months ago

                    Meta is a company whose business model depends on exploiting the data it gathers, and its privacy policies are carefully written to give it as much flexibility as possible. It’s true that if you’re on an instance that federates with Threads you’re assuming that risk. If you compare their language to a policy that’s written with a goal of privacy – like eu.social’s the differences are clear.

                    Please stop putting words in my mouth.

                    OK, then, speak for yourself: do you see instances that federeate with Threads as being part of Meta’s ecosystem?

      • Valmond@lemmy.mindoki.comEnglish
        2·
        9 months ago

        But where will meta put its ads, and how can it filter what you see if you can’t (as a user of an instance blocking meta/threads/…) subscribe to meta instances?

        I mean it’s just a hot mess, so I’m all for blocking those predatory psycopaths even if it theoretically isn’t needed in some cases.