Due to some disgusting behaviour, I’ve kicked off the process of deleting ALL images uploaded in the last day.
You will likely see broken images etc on aussie.zone for posts/comments during this period of time.
Apologies for the inconvenience, but this is pretty much the nightmare scenario for an instance. I’d rather nuke all images ever than to host such content.
It seems that lemmy.world has decided to move to application based sign ups - which may slow some people down, but from a mod perspective the only options available are bans of custom length, removing comments/posts and locking posts
Yes lemmy’s modding features are… lacking. However there are some non-lemmy services availble to stop this sort of thing that I’m looking into.
All options seem like a headache for mods really.
What I’d really like is a “freeze community” button, so if stuff starts getting out of hand we can lock all of the posts and deal with it. But what we really need is a proper CSAM filtering tool on instances to reject posts before they get cached all over the fediverse
Trouble is the target communities have (so far) not not been on our instance. There’s little we can do about what a user from another instance posts onto another instance. We see that content through federation, but don’t directly control it.
Federated moderation? I’m spitballing, but if you could nominate instances that you ‘trust’ you get a virtual mod team to attack these issues, and spread across TZs.
if the mod tools aren’t there yet, we’ll I guess it’s moot…
Something like LemmyA instance is banning ZCommunity. They are in my trusted mods, so follow what they are doing. No doubt a simple thought, with many cases not considered (different trusted servers with opposing mod settings)…
It would probably be better to have virtual mod replication to be incident based…