FediBlock meta
Sometimes, instance admins / individual, non-admin users should investigate shit before either posting on #FediBlock at all, or taking what's on #FediBlock for being true at all.
As the most recent example, the hashtag currently contains at least two instances that should not be blocked, and were merely targets of a malicious Pleroma MRF.
re: FediBlock meta
@kescher wait, somebody used MRF to frame someone? pog
re: FediBlock meta
@ariadne that MRF pretty much didn't work as intended when interacting with software that wasn't Pleroma, or at least its impact was simply larger on instances with Pleroma. That's as much as I currently understand, which is very little.
re: FediBlock meta
Pleroma does not trust forwarded remote content, or at least, did not in the Pleroma 1.x days, so any malicious MRF would be limited in scope to the instance where it was deployed.
FediBlock meta
@kescher o??? what instances were good?? am not sure if i know what post ur referring to tho since i cant see hashtags
FediBlock meta
@kescher o alright thank u! yea i didnt see this post n already had hunk city suspended for different reasons
] Gerblin Taffer 
FediBlock meta
@kescher I've treated Fediblock as a "suggestion"; one can't take the tag at face value.
Moderators and admins are responsbile to actually check if an instance is offending or not.
Re: FediBlock meta
Yes, the responsible thing is for the admin or the user blocking to *always* verify the claims, but it'll be so much easier on everyone if the work is done upfront. Especially because the person reporting the instance/user is already looking at said bad instance/user.
Re: FediBlock meta
re: FediBlock meta
I am starting to understand why some mutuals dislike the hashtag, even though that's not how I am using it at all.