So what happened? We manage our defederation process with fediseer. It’s a system that allows us, instance admins, to follow the defederation happening on other selected instances. We generally follow the defederation of sh.itjust.works, lemmy.dbzer0.com, literature.cafe, lemmings.world and a few other instances that have proven to be trustworthy in the past. However, in most of the cases I will also review them manually instead of blindly following them. That’s why I added a censure for ani.social with tag “Loli” as was being reported - contrary to the “CSAM” that was being reported by Lemmy.ml.
When I was informed that might have been a mistake I delved a bit deeper and saw there was indeed no proof of any CSAM or even LOLI being posted - and I deleted the censure and we federated again. After this I made a post on the ani.social instance about what happened.
We always put censures in Fediseer to be as transparant as possible but we usually don’t announce blocks on CSAM, Loli or Spam instances. Why? Because for Loli and Csam we don’t want to give those instances extra exposure by announcing them. And for Spam, there’s just too many and it would be hard to keep up.
We really can’t afford to have the most popular lemmy instance behaving like this. The LW admin team has generally shown more professionalism in that past, so what gives?
Again, yes we were quick on the buttons but the csam/loli blocking is treated in a “better safe than sorry” way. We do this to keep our users and team safe. And everything was corrected within an acceptable time imo.
They refederated a couple hours ago (source). @antik made a post clarifying things over in the meta thread on ani.social’s site and cleared things up.
I understand people’s frustrations with seemingly arbitrary moderation decisions like this sometimes, but I wouldn’t want to be in their shoes making calls like that for a large instance like this. It is heartening to see that the review process did not take long and the decision reversed fairly quickly (<12 hours). This stands in contrast to the lemmy.ml admins that defederated ani.social for seemingly no reason and locked all discussion about it and it still stands. So, props to antik and LW admins on this one.
I don’t really know that instance, since I just filter out pretty much any anime-type content but it would be nice to get at least a short announcement when lemmy.world de-federates from other instances.
They do generally give announcements when they defed from larger instances. But they are also constantly defederating from numerous spam instances and such that are constantly popping up so making a dedicated anouncment for each one is a bit much. They do however do a good job with keeping fediseer updated whith all of the instances they defederated and the reason. So if you want specific info on smaller instances then I would check there.
Considering I spend most of my time on Lemmy just scrolling through all and I don’t recognize the instance OP mentioned, I’m assuming it is a fairly small.one and the LW admins didn’t see a reason for a full blown announcement.
Yeah, probably. Aside from the fact that Dessalines and Nutomic aren't actually trustworthy, it's still a bad idea to blindly follow these kinds of decisions. I'm all for instances curating how they want to, but that requires them to deliberately decide for themselves, not just delegate to an outsider with an entirely different editorial policy.
I’m also experiencing this problem, however I don’t see anything about being blocked by Cloudfare. What I do see in the network tools is that on the image’s POST request, Lemmy is returning a 400 (Bad Request) error. Issue is happening on both the normal Lemmy UI and the Photon UI.
support
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.