🇳🇱
Apparently thanks in part to my article about Eugen caving to a Nazi's misinformation campaign there is an effort to defederate from matodon.social (not something im promoting directly myself)... Several of his users are getting scared and starting to question if they should stay.
I may not want M.S defederated, but maybe Eugen should not cave to Nazis then...
@freemo "defederate from Mastodon.social?" Is that an action on Qoto.org's part or the Mastodon instance community as a whole shunning (essentially blocking) them? I am painfully, awkwardly new to this scene. Words mean things but I'm not clear the effect.
There's been ripples in the wider Mastodon community for several days about mastodon.social's moderation, and people have been actively moving away from it. I hadn't seen talk about defederation, but it makes sense that people consider it if it's problems are being exposed one by one.
@digital_carver @freemo The big problem, as with so many issues from Socialism to Capitalism to Libertarianism is things would likely work just fine... if only you got rid of all the people and I mean ALL the people involved.
Isolating the instance maintained by the same person maintaining the code base is... not a good plan, if I understand the dynamics. Forking the code would only make sense if there's a better plan than, "Gee, I hope the one person holding all this together has his crap together as well."
In general I agree with you and *don't* want defederation to happen unless absolutely necessary.
But mastodon.social shouldn't be immune to consequences just because the lead developer has a hand in it. Letting the codebase be held hostage in that way would defeat the entire point of the Open Fediverse idea. We should treat it like any other instance and consider it if things ever get bad enough to justify it - **but** in this case I think there's still room for communication and correction, and I hope things get resolved in a friendly way.
@digital_carver
Pointing out truth and shedding light on management decisions willfully based on lies and misinformation rarely if ever result in a humble "mea culpa."
There "should be" consequences, but perhaps you have heard, " 'should' into one hand and shit in the other, see what fills faster?"
The design for Mastodon was not set up to explicitly forbid technical arbitrary control over the entry list. Therefore it is compulsory the one who maintains the code also assert arbitrary control over the entry list. The only meaningful solution is to design that out of the platform. Pass that past the one who maintains that. Good luck.
@freemo