@fre_d The short version is that folks who are no-coders and have been actively involved in the dev side of mastodon feel they are being ignored and disrespected. Three examples I've seen:

Non-coder proposing a change and making a mock-up of how it could work, change implemented, coders give no credit to person who suggested it.

Non-coder dev points out that coder devs are ignoring issue, get's told to code it themselves (obs, they can't, they aren't coders.)

@fre_d

Non-coder dev folks told to create their own version of Mastodon if they don't like it.

As a result the non-coders involved in Mastodon development are either getting off mastodon entirely or, yes, looking into if they can get enough interest to start their own version of Mastodon.

So non-coders in general aren't being driven off Mastodon. But non-coders WHO ARE INVOLVED IN MASTODON DEVELOPMENT are. And those non-coder devs are the main communication between coders and users.

@jessmahler while I agree that telling people to code something (especially if they can't) is rude. I don't agree that people who propose ideas deserve to be credited however, as doing that so is relatively trivial in my opinion.

When I propose a pull request to be merged to an open source project, I don't expect to be credited unless I do something major.

As for issues being ignored, a lot of work goes into managing a large open source project, especially of this scale.

@fre_d Not interested in arguing. I've never been involve don the dev end and I don't know what goes into it.

What i KNOW is social dynamics. Like I said, right and wrong don't matter here. What matters from a social dynamic perspective is those non-coder devs were the main avenue users had to communicate needs to coding devs. Without that avenue of communication, user experience will degrade as user needs/concerns aren't heard.

And users will start leaving.

@Sylvhem Good point, and potentially indicative of the deeper problem. But as a non-tech person, I'm USED to hearing about coders getting into it with eachother and going off to do their seperate projects. It seems to be a normal part of the tech process.

And from a social dynamics perspective, (which is my geek) it's the loss of the people who can translate between the coders and the end users that will do the most harm, long-term

@jessmahler I agree with you on that.