@freemo I don't believe the answer to, "this instance is being unfairly targeted and ostracized" is "let's ostracize the instance controlled by the guy playing along and BTW he maintains the code we all run on."
If the code is really open, forking the code to break control over the entry list would be a better option, but that only presumes a better option than "we trust that one guy has his crap together" exists. A "democratic" committee solution simply invites Truth Social to take it all over. It's hell getting people to join as it is without some complex scheme for a server list to on-ramp people to Mastodon.
Sometimes all options suck.
@Romaq Agreed, we need someone who isnt negligent running this shit.
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.
Many threads mention me trying to get them defederated and link my article.. so people seem to have gotten that impression... But as I said that isnt my intent. My intent is to expose the truth, what consequences that has is on Eugen not me.
@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.
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.
@digital_carver @Romaq @freemo
Mastodon.social and Gargron are toxic.
@Romaq That is something the community is doing. I have not asked nor supported the idea of defederating from M.S