this post was submitted on 04 Sep 2023
17 points (74.3% liked)

Programming.dev Meta

2466 readers
2 users here now

Welcome to the Programming.Dev meta community!

This is a community for discussing things about programming.dev itself. Things like announcements, site help posts, site questions, etc. are all welcome here.

Links

Credits

founded 1 year ago
MODERATORS
snowe
Ategon
17
Defederation requests, how to? (self.meta)
submitted 1 year ago by natecox to c/meta
16 comments fedilink hide all child comments
 

Do we have an established practice for requesting defederation?

I would very much like to request that we defederate from burggit.moe (because I would prefer to keep my lemmy experience free of loli porn) and I went looking for the best way to do this, but the best I could come up with was posting to meta and that seems like the wrong place.

I feel like I missed something obvious ¯_(ツ)_/¯

you are viewing a single comment's thread
view the rest of the comments
[–] natecox 0 points 1 year ago (1 children)

It is very literally depictions of children engaged in sexual acts, which fits the legal definition of CSAM where I live.

Blurring is done at the client level by applying a filter to the images so even with blurring on, the (illegal where I live) image is downloaded to my computer regardless of if I actually see it or not.

[–] Scoopta 1 points 1 year ago

Doesn't change the fact that it's not illegal in a lot of countries because it's drawn art and not abuse which is the A in CSAM. That instance is in the Netherlands where I believe Loli is legal for the reasons I've mentioned...anyway the point of my bluring comment was you could blur it...which is on the client level so you don't have to see it in order to block it. I wasn't suggesting the blur as a permanent fix. Also if you're that worried about browser cache just use private browsing or something so the cache is immediately wiped afterwards...but whatever. Also mere fact that you know what's on the instance means you must have seen something by accident...so it's already in your browser cache so that's a moot point anyway.