Comment on The free fediverses should emphasize networked communities

• dipshit@lemmy.world ⁨11⁩ ⁨months⁩ ago

  I pretty clearly described the difference in “data” between the data we want and data we don’t want. Try re-reading that and if it still doesn’t make sense I’ll explain in more detail.

  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.

  Buddy, that’s the internet:

  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

  This is how data is exchanged on the internet. It’s less of an agreement and more of a protocol. If you’re trying to claim here that an artist putting up a peice of work on a fediverse site means that facebook now has full rights to that work, I think you’re mistaken. Yes, as part of how the fediverse operates, if you are federated with my server, you are giving me permission to federate the federated content with my server’s users. This is currently happening right now across all federated instances.

  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.

  It’s a shame, because we have the same goal in mind: not being tracked by facebook / meta. We aren’t on opposing sides of this issue. My point is that defederating from meta doesn’t stop meta from tracking you online. If you want to stop meta from tracking you online, you need to do the following:

  1. don’t participate in meta’s services. This means facebook, instagram, threads, the entire ecosystem that meta has created. Deactivate, delete your accounts, etc.
  2. don’t participate in the fediverse via meta’s servers (this is the same as #1 really).
  3. Use an anonymous handle on the fediverse
  4. Use a modern web browser that is up to date (which blocks 3rd party cookies by default, or configure your browser to do so)
  5. Block content from facebook domains at a router level if possible to protect your entire house.

  Defederating isn’t on the list because defederating from meta doesn’t stop meta from tracking you.

  source

  • thenexusofprivacy@lemmy.blahaj.zone ⁨11⁩ ⁨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.

    source

    • dipshit@lemmy.world ⁨11⁩ ⁨months⁩ ago

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

      Threads is a company and it needs a legal document to describe how the social media site operates. A website needs to copy and distribute content in order to show content. Federated websites need to copy and distribute content from other federated servers and their own server in order to show content. This is how lemmy.world and blajah.zone can speak as if we are on the same server. Each fediverse should also include a similar privacy policy as it describes how their content is distributed on the internet. Facebook’s privacy policy likely describes how your content may be seen on other facebook products and in facebook apps. These legal documents spell out how systems operate. You assume a similar risk with each site you operate on.

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

      (data, ‘data’, data, “data”) are all the same term. Let’s use better terms:

      • posts (the content that you give to a federated site: your handle, your comments, your OC, etc…)
      • public identity (the information about who posted the content that is publicly accessible: e.g., your handle, your display name, bio, profile picture, maybe your IP address, user agent, email address, matrix handle, skype, other contact info if you’ve provided it and if that instance makes that information public)
      • private identity (the information that we assume will be kept private and not shared with others: the token that identifies you to the server via a 1st party cookie (i.e., your “token” that allows you to stay logged into the site you are currently using), any personally-identifyable-data (PII) that you may have given to a site in order to operate - not something that I’ve seen with lemmy sites but would be true if you’ve ever had to upload this information to the server, such as with setting up an account with a financial institution, basically anything that could be used to track you, specificially online and offline.

      Facebook is evil for a lot of reasons but their original sin was the 3rd party tracking which, thanks to their assets (images) being put everywhere because site owners wanted better SEO and engagement with facebook users, facebook could send a cookie with a random id that specifes some user as it travels from site to site and then link that random id with the facebook user when that user logs into facebook. This allowed facebook to track its users everywhere on the internet. However, this didn’t allow facebook to identify non-facebook users like it could with facebook users. All facebook would end up with when tracking non-facebook users is information about what a random user viewed on the web - this isn’t great (and can only be stopped if you just block facebook at the router or browser level) but at least that user stayed anonymous. The motivation for this tracking was to push more targeted advertisements to facebook users, where facebook actual stands to earn a profit. There isn’t a lot of profit in just identifying users online if those users stay anonymous… except of course of internet advertising (programmatic advertisements). This is why it’s also important to interact with sites which do not have programmatic advertisements - these are most advertisements now a days, especially if that ad feels targeted specifically to you based on a site you’ve been to. You want to worry about tracking, look into how the programmatic ad industry works - of which facebook is a part but most importantly doesn’t involve federation because that’s something totally separate and something which actually protects against tracking.

      Think of federation as a site downloading an image and reserving it to you. Tracking happens in the serving of an asset (image, video, etc), so if you are getting that content from the site you trust won’t track you, then … you won’t be tracked. A nasty site that wants to track you cannot get your information via the fediverse, since the federated site simply copies and privately redistributes the copy to its users, leaving the nasty site only knowing that “this instance with thousands of users received our content” - not very useful for tracking, advertising or for ad revenue, doesn’t provide any data that would be valueable for data sellers either.

      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.

      Please stop putting words in my mouth. I am capable of speaking on my own terms. Also, by your perspective, a server that receives and processes email from meta is part of meta’s ecosystem. That statement would be correct if you replace “meta” with “the internet”.

      Also, why are we discussing this with Meta when there’s a log bigger threat out there (ABC/Google, search engines and scrapers)? And by “threat” I mean “how the web has always operated”. I feel like writing an application that showed users how easily they could be tracked on the fediverse even if that instance were not federated by any other servers.

      source

      • thenexusofprivacy@lemmy.blahaj.zone ⁨11⁩ ⁨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?

        source

        • -> View More Comments