I created this post on my local server, calling for what I thought was reasonable action against a self-proclaimed threat to Canada.
Someone in the community disagreed (fine), and reported the post on their hosting instance (lemmy.world), which led to an immediate deletion of the post (on that single instance only).
Think is, I really don’t feel that it was warranted - and neither do most of the community members over on lemmy.ca.
I realize that instances are autonomous, but is there an appeal process to potentially have this reinstated?
This has been an interesting bit of discussion, to say the least. Different instances with different local rules are going to lead to problems like this situation more and more, as lemmy grows in popularity. It’s inevitable, and we’re all going to have to sort it out as the platform matures.
However the more I think about it, the more concerned I am that removing individual posts (or even comments) on a federated instance has the potential to misrepresent communities, through the filter of each instance’s mod/admin biases.
Perhaps a pointer saying “this post was removed on lemmy,world for violating rule (x), and can be viewed on its original instance <link>” would be appropriate. Or alternatively, blocking entire communities with a comparable stub: “lemmy.world has chosen not to federate community@instance.”
Of course in my examples I’m picking on lemmy.world because that’s where this is happening, but the problem and possible solutions are true for all instances.