As the Fediverse grows more and more, rules and regulations become more important. For example, is Lemmy GDPR complient? If not, are admins aware of the possible consequence? What does this mean for the growth of Lemmy?

  • cwagner@lemmy.cwagner.me
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    I (with my own single user instance), do not. As soon as you offer your service to other users, it’s different. If you are a company or not, does not matter.

    • heartlessevil@lemmy.one
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      1 year ago

      This isn’t true since your single user instance is federated. For example, this comment is going to end up on your instance, and it could have my personal data.

      edit: here’s a meta-link to this comment on your instance: https://lemmy.cwagner.me/comment/2786 – despite it originating from lemmy.one and the post being lemmy.ml from a user on lemmy.world (interestingly every person involved in this interaction is on a different instance)

      • cwagner@lemmy.cwagner.me
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        That is a very different way of looking at it. I take the view of this Lemmy privacy policy that you are essentially sending your comment to me, just like an e-mail.

        Though unlike an email, it’s public on my instance for now, so yeah, you have a point there.

        My eventual plan is to make my instance only visible for logged in users (= only me), but I heard that for now that (the private instance flag) is not possible with federation.

          • cwagner@lemmy.cwagner.me
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            You can disable most endpoints in your application firewall, or put them behind a whitelist. For federation to succeed you don’t need all that many publicly reachable endpoints (mostly a bunch of inboxes and the data for your own user account).

            Is there a guide somewhere? Because experimenting when federation is already as unstable as it is, is hard.

            My post will end up on your server but also on the server this community is hosted on, from which it’ll end up on hundreds or thousands of other servers. I’ve never agreed to any of their privacy policies and terms of service and neither has anyone else here.

            Just like with e-mail, yes. Sending an e-mail to [email protected] does not make you agree to the example.org TOS and PP. Or more relevant to federation, sending an e-mail to a mailing list will end up on hundreds of servers. This is not that new a concept.

            • Skull giver@popplesburger.hilciferous.nl
              link
              fedilink
              arrow-up
              3
              ·
              edit-2
              1 year ago

              I don’t have a guide for you, sorry. I’ve looked into it briefly but I can’t say I care enough to fix it.

              I’m pretty sure you’ll be able to go federation only by blocking everything that’s not an application/ld+jsoncontent type (technically application/ld+json; profile="https://www.w3.org/ns/activitystreams" but some servers don’t send the correct Accept headers). The Lemmy frontend submits plain JSON and POST requests and it doesn’t implement the client-server ActivityPub API, so that should be the easiest way to keep federation working while whitelisting your personal IP addresses.