User Generated Content and the Fediverse: A Legal Primer
www.eff.org
A growing number of people are experimenting with federated alternatives to social media like Mastodon, either by joining an “instance” hosted by someone else or creating their own instance by running the free, open-source software on a server they control. (See more about this movement and joining...

I found this interesting and was wondering how some of the larger instances handle the issues they outline such as

Copyright/DMCA Safe Harbor CSAM Law enforcement/warrants/info inquiries

And not included (since it’s focus is on US legal issues) but I’m curious about would be other regulations such as EU user data retention

  • @SzethFriendOfNimi@lemmy.worldOPEnglish
    2•1 year ago

    Not sure. I’d guess they do if they’re in a country that has a mutual IP treaty with the US but that’s definitely a question for a lawyer.

    I can imagine that even hosting your own instance that copies down the content and only federates out your comments or non copyrighted material can be tricky depending on how the fediverse works (where’s an uploaded image kept when it federated out to a server?).

    Is there a copy or just a reference to the original instance?

    I’d be really interested in knowing how that works

    • @usbpc@programming.devEnglish
      2•1 year ago

      Is there a copy or just a reference to the original instance?

      My understanding is that the actual full size image is held just on the source instance, but that thumbnails are cached on other instances for a time.

      But looking into the official documentation there seem to be json files missing and the descriptions are not completly clear: https://join-lemmy.org/docs/contributors/05-federation.html#post

      And just looking around using inspect element to see the HTML source it seems that even the thumbnail is not cached for external directly hosted on lemmy image posts. But then again I also could the the preview of a image post earlier while the full size image was not visible as the hosting lemmy instance was offline.