Is that different for Lemmy? If so, why is PieFed’s approach to private communities different from Lemmy’s?

  • chisel@piefed.social
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 month ago

    It’s not a risk of content exposure. By definition, risk is something that may or may not happen. Federating private content is guaranteed content exposure.

    There are websites that make it easy for anyone to see exactly who voted on a post. In a similar way, making a site that ignores or highlights private content is an inevitably. Not to mention federated software that doesn’t even know what private content is and will publish it with no malicious intent.

    It’s very easy to federate and create your own federated database without the intent of actually using it for piefed/lemmy/etc… It’s one of the biggest downsides to the fediverse: privacy is impossible. Absolutely nothing is stopping Facebook, Google, or anyone else from setting up an instance and gaining direct access to all federated data.

    • julian@activitypub.space
      link
      fedilink
      arrow-up
      3
      ·
      1 month ago

      Yes I think you’re right about that. The nomenclature is important to get right because once federation is added to the equation privacy (without some form of E2EE) cannot be guaranteed.

      So perhaps calling it something like a gated community (like @ex_06@slrpnk.net said) would help, although that term has some other associations with it too 😝