sh.itjust.works Main Community

7694 readers

3 users here now

Home of the sh.itjust.works instance.

founded 1 year ago

MODERATORS

[email protected]

103

De-federate from instances with loli (sh.itjust.works)

submitted 1 year ago by [email protected] to c/[email protected]

140 comments fedilink hide all child comments

Can we get a consensus on whether our community should de-federate with servers that host loli? I personally think we should block them, and if that ends up not being the consensus here then I'll probably sign up on another server. I hope we can all agree to set that boundary though because I like it here and it seems otherwise pretty cool.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (6 children)

Absolutely block instances hosting illegal content - the way federation works means copies / caches of content can end up on this server? Or even if that’s not how lemmy does it, it risks using this server to facilitate the spread of something incredibly harmful & damaging.

As far as I’m concerned there’s no argument for allowing / normalising content produced which quite literally ruins peoples lives.

Edit: Even stuff that’s purely cartoonish in nature for me is just grim, and I don’t want to be a part of a community which supports it.

Edit2: If a server can block a specific community posting CSAM then maybe that's a better solution than blocking the underlying infrastructure. If that's not possible, I think defederation is the only real way to deal it, as frustrating as that would be for legitimate users.

[–] [email protected] 5 points 1 year ago

That's not how it works. Instances don't cache images from other instances. If you hover your mouse over an image you can clearly see the site it's hosted on is in fact not originating from the instance you're browsing on. It works like Pleroma, Akkoma, Rebased, and other Pleroma forks.

IANAL, but I believe you can't be held liable for hosting links to other images on a site, regardless if they're embedded through the website's UI. They're not stored there, afterall. The client is rendering them.

All that gets cached, I believe, is the text and users from remote instances. And by cached, I mean stored in the postgres DB.

load more comments (5 replies)