The legal environment around Lemmy is tenuous at best. Content and / or actions that are legal in one nation are illegal in others but Lemmy caches that content on every federated instance with active users.
To illustrate the complexity involved consider a Mexican user on a Lemmy instance located in Germany that visits exploding heads to view Nazi content. Which nations laws are controlling?
What about when an Australian user on a Finnish Lemmy instance who accesses something like fauxbait from lemmynsfw.com? Those images are arguably illegal in Australia but who has liability here? The Australian user? The Finnish Lemmy instance? Lemmynsfw.com?
In both of those scenarios the User is one country with its own set of laws, the Users Host Instance and its content cache are in a 2nd country with a different set of laws, and the instance hosting the content is in 3rd country with yet another set of laws!
It’s the same problem with digital piracy, who is legally liable when the law, and remember we don’t even know whose laws apply, is breached? The User? Their Host Instance? The Content Host? All of them?
Legal lightening is absolutely going to strike a Lemmy instance soon and no sane instance operator wants to be the lightening rod.
Just replace “Lemmy instance” with “blog”, and the answer is obvious.
“consider a Mexican user visiting a blog located in Germany to view Nazi content.”
The user is subject to Mexican laws. The blog owner would be subject to German laws. The instance owner is likewise subject to German laws.
Adding additional parties doesn’t change anything. For example, if a Mexican user on a Swiss VPN views content originating from a blog in Germany, then the user, the VPN, and the blog are all subject to laws of their own jurisdiction.
Those laws can regulate what content you can access, what content you can host, or both.
If you are American then your Lemmy instance is most likely be protected by section 230, and you probably don’t have to worry too much about non-pirated content. If you live in another country or host pirated content in the US, then YMMV.
Just replace “Lemmy instance” with “blog”, and the answer is obvious.
Actually it’s not because there’s no 3rd party like there is with Lemmy and especially not a 3rd party that’s keeping a cache (copy) of the content.
If you are American then your Lemmy instance is most likely be protected by section 230…
So there’s no American users on lemmy.ml, lemmygrad.ml, hexbear.net, or even lemmy.world itself? You’d be very very wrong in that assumption.
or host pirated content in the US, then YMMV.
Aaaand we are back where we started. What is “hosting”? Your lemmy “home”, lemmy.today for me, has a cached copy of all the content it’s users view. So if I retrieve illegal material my instance has it too and while it’s hidden it IS retrievable by both the Instance Operator and other users (if they know how).
So whose door(s) are the cops kicking down in the raid? Mine? Lemmy.Worlds? The one at exploding heads / lemmynsfw / db0zer? All of them?
The legal environment around Lemmy is tenuous at best. Content and / or actions that are legal in one nation are illegal in others but Lemmy caches that content on every federated instance with active users.
To illustrate the complexity involved consider a Mexican user on a Lemmy instance located in Germany that visits exploding heads to view Nazi content. Which nations laws are controlling?
What about when an Australian user on a Finnish Lemmy instance who accesses something like fauxbait from lemmynsfw.com? Those images are arguably illegal in Australia but who has liability here? The Australian user? The Finnish Lemmy instance? Lemmynsfw.com?
In both of those scenarios the User is one country with its own set of laws, the Users Host Instance and its content cache are in a 2nd country with a different set of laws, and the instance hosting the content is in 3rd country with yet another set of laws!
It’s the same problem with digital piracy, who is legally liable when the law, and remember we don’t even know whose laws apply, is breached? The User? Their Host Instance? The Content Host? All of them?
Legal lightening is absolutely going to strike a Lemmy instance soon and no sane instance operator wants to be the lightening rod.
Just replace “Lemmy instance” with “blog”, and the answer is obvious.
“consider a Mexican user visiting a blog located in Germany to view Nazi content.”
The user is subject to Mexican laws. The blog owner would be subject to German laws. The instance owner is likewise subject to German laws.
Adding additional parties doesn’t change anything. For example, if a Mexican user on a Swiss VPN views content originating from a blog in Germany, then the user, the VPN, and the blog are all subject to laws of their own jurisdiction.
Those laws can regulate what content you can access, what content you can host, or both.
If you are American then your Lemmy instance is most likely be protected by section 230, and you probably don’t have to worry too much about non-pirated content. If you live in another country or host pirated content in the US, then YMMV.
Actually it’s not because there’s no 3rd party like there is with Lemmy and especially not a 3rd party that’s keeping a cache (copy) of the content.
So there’s no American users on lemmy.ml, lemmygrad.ml, hexbear.net, or even lemmy.world itself? You’d be very very wrong in that assumption.
Aaaand we are back where we started. What is “hosting”? Your lemmy “home”, lemmy.today for me, has a cached copy of all the content it’s users view. So if I retrieve illegal material my instance has it too and while it’s hidden it IS retrievable by both the Instance Operator and other users (if they know how).
So whose door(s) are the cops kicking down in the raid? Mine? Lemmy.Worlds? The one at exploding heads / lemmynsfw / db0zer? All of them?