Why YSK: Choosing an instance with defederation policies you’re most comfortable with is important to make your Fediverse experience smooth in the long run.
Here is a chart showing the defederation count of each instance.
| Instance | Defederated with how many other instances |
|---|---|
| beehaw.org | 405 |
| feddit.de | 101 |
| lemmy.world | 63 |
| lemmy.ml | 44 |
| sh.itjust.works | 4 |
| exploding-heads.com | 3 |
You can get it by going to the instance’s instance list and scrolling/Ctrl+Fing down to “Blocked Instances”. To find the instance list, go to https://your-instance.url/instances, for example, https://lemmy.world/instances
Pretty sure there are no significant instances that allow child porn.
That would depend if you think lolicon or hentai of canonically underage characters in general is CP or not.
Doesn’t matter in the case of Beehaw though because they defederate from any instance that allows pornographic NSFW content of any kind period - as do probably a majority of instances, at least until Lemmy creates better filtering systems.
Beehaw federates with porn instances like lemmynsfw.com
Indeed. Hence, no one was all that bothered by the defederation from a large list of small instances with problem material. The question is “why is the number so high” and that’s a large part of it
With the federation system, if you run a Lemmy instance and one of your users subscribes to an instance that hosts CP, does your own server end up hosting CP? Or does Lemmy tell the browser to retrieve the actual content directly from the original server?
My understanding is that the image is still hosted wherever it is normally (probably the original Lemmy instance) but everything else from the post and comments come over. I’m not sure how well that would fly in a court when you can still access it via
yourinstance.com/c/cp@badinstance.com.