Legal considerations of self-hosting Lemmy instance
Hi everyone,
I've been wondering about legal implications of self-hosting Lemmy. Isn't it universally required in many countries to moderate the content that you host publicly? What happens when someone posts something illegal on your instance and you don't won't to bother with being a mod and just enjoy the technical aspects of it?
As much as I disagree with some of them, I recall the folks at the Accidental Tech Podcast spent a good while on this very discussion back when people were migrating from Twitter to Mastodon, and they had some interesting concerns and conclusions.
The answer is yes, in many places the admin hosting the content could be responsible for the content. Where I live I believe they would have to provide user data about who made the post, and if they refuse, they become the responsible party.
Interesting, I wonder how does decentralized nature of fetching data from other instances affect this. Thanks for providing the reference! Will look into it.
If you don't want to moderate, don't let others sign up to your instance. That deals with pretty much all your legal issues.
For US-based people, register for DMCA notifications. This means if someone posts copyright infringing content, you get a message about it instead of your hosting provider, and you get to remove that content instead of your hosting provider removing your account.
Check about GDPR compliance. Part of that is fully deleting user content in a timely fashion when they ask. I've heard that Lemmy might not be good about that, but I'm not sure. If you have any EU users, you'll need to comply.
If you want to run a large instance, you'll need to have a plan regarding CSAM.
If you do moderate, use The Bad Space or shared block lists to defederate from the the most problematic instances. I'm not sure whether they've really made it to this general corner of the fediverse, though.
That said, there's no particular requirement that a DMCA notice be sent to you even if you have a registered agent and some reporters will send it to the abuse contact for the IP netblock you're hosted on regardless of registration, so you may want to make sure you understand what steps your provider may or may not take when they get a DMCA notice before you actually get a notice.
You can set your instance to private and close registrations, which is what I am doing. That way you can use it only for yourself and a few friends and still be connected to the fediverse. The communities that you make on your self-hosted instance wouldn't be connected, though.
If I set up my private instance for the purpose of interacting with other, popular, servers, can I save my comments locally? I'm referring to comments I make on another host, such as lemmy.ml I'm trying to understand if there is a way to keep my content in the event that the other server disappears.
I just double-checked and logged into the psql docker container and yeah, your stuff is safely stored as well as all of the other content that is synced up. So, if you sync with gaming@beehaw.org all of the stuff you see on the front-end will also be stored in your local database, including your own content of course. I do not think this includes images that were not uploaded on your instance.
Edit: now I'm not sure about the images, I checked the images folder and it's almost 1 gigabyte. I've uploaded 0 images. Not sure if it's a cache or if they stay there forever.
Well, as you mentioned before it's to enjoy the "technical aspect", which could be many reasons. For one, if the instance you signed up on shuts down there goes your account with it. I feel better self-hosting because I am in control of when/if it shuts down.
One of the devs mentioned that the biggest draw on server resources is the direct web interaction, and loading pages, not the behind-the-scenes federation, where the database queries are simpler and the actions can be queued up and retried as needed. (I think apps would have the same issue since the server's going to be doing the same kind of massive database queries to build your feed.)
If your comment takes a few minutes to get from your home server to another one when the site's overloaded, it's not a huge deal, but if your comment takes a few minutes to get from your browser to your server, the site's basically down.
So moving yourself to a new server takes over the entire real-time load you would have been using, and the additional background load of sending threads to/from your server is a lot smaller.
As far as I understand, at least the Text Data (posts?) is replicated to your instance. So if you are only 1 person using your own instance, I think it should neither hurt not help the network. But if there are 2 or more people using your instance (Family / Friends) and they are interested in some of the same content, they will fetch that content from your server and not from the original servers (minus the pictures AFAIK). So it causes a bit less stress on the server that hosts the content your users are consuming.
I am all new to this, so take this with a grain of salt.
At the very least (and a sizable concern) is that any images you upload would at least be stored on your server. At least I think. Also self hosting...