The kind of drama happening now (ie. devs ignoring specific requests put forth by some users) is the natural outcome of the benevolent dictatorship model and proves that, no matter how decent, good and caring a person is when starting a massive FOSS project, they are ALL bound to reach the "I make the rules" stage, because that's the nature of human beings when exposed to massive stress.
Let's stop #ForkOff and make #Mastodon a #Cooperative NOW!
@Antanicus By all means fork the software and build a stronger network as a result.
But the story that the lead developer was ignoring requests is just false and even insulting. He was implementing an oft-requested feature and responding to concerns. Then a few people started piling up abuse because they weren't getting exactly what they wanted.
@Antanicus
I think the point about the need for democratic or cooperative governance are apt, but saying what we saw today were devs ignoring the community is not true, and quite detracts from your important point.
@eladhen
> saying what we saw today were devs ignoring the community is not true
- apologies for putting my ideas down too bluntly. I didn't mean any disrespect for those working hard on Mastodon, I just wanted to express my ideas around a trend that's been affecting FOSS projects in general.
@Antanicus
I completely agree on that.
@Antanicus 1/2 I can't help thinking that this is not going to work. You can't force @gargron to change his development model, or to develop things that he doesn't want to do. Nor should you be able to.
So the only option is to fork or use something else. That's just the way it is.
Complaining that you can't fork because you can't code is a moot point because the only option is to fork, and AFAIK code doesn't write itself. If you can't code the fork will have to find someone who can....