@silverpill @pepper0

I made a similar case to @erlend and @zicklag some time ago, relating to #Muni town's #p2p technologies.

If one is content with small uptake, and maybe earning sustainable income from that for a small team, or even a decent SMB or mid-sized business, then all is well.

If ones ambition level is larger than that, things are a whole different matter, and much more forces need to be accounted for.

At Social coding commons the #FSDL considers these..

https://coding.social/introduction/#free-software-development-lifecycle

@silverpill @pepper0

With #Solid project you saw a "Just create intricate #LinkedData specs, omit appealing to dev community, target biz directly. And broad adoption will come".

With #ActivityPub we saw "Let's have these initial specs be the basis, and throw it into this grassroots ecosystem, and vNext will rise from that".

#DAT project saw cryptography and compsci experts going deep in the tech, without considering how it would be adopted, implicit "code it and they will come".

Etcetera.

@thisismissem One of the biggest problems, in my humble opinion, is the over promise under deliver. We constantly see toots telling us what is coming, or giving dates, and it doesn't appear. I have lost count of the number of these toots that are then deleted at a later date. I did keep a copy of a toot that was posed by Dan a few weeks ago in which he promised to stop over-promising. It was deleted about an hour later.

Dan the Dev is too thinly spread. He has great talent, but works on far too much. The result is that things suffer. Projects and promises lapse. People get frustrated. Tempers flare. Dan gets pissed off, understandably. Then come the churlish toots

One could argue that we have no right to dictate his workload. However, he's putting out a product (products maybe?) and it comes with responsibility and expectations from the 110k active users. And what about the people who gave up their hard earned cash to fund over $100k to his projects. What was the plan there? I've never seen any firm strategy. Where's the crowdfunding being used?

People want to help him. I have offered several times over the years. I have a list of crap UI issues. I've offered/suggested that he needs to test stuff before launch. If he has a test group, it's not working .... and it can't be your friends! Testing is a thorough and serious aspect of software dev. It's not happening here.

He's hinted at a new team. He has been asked to introduce this team. I'ts never happened that I have seen, and the messages go unacknowledged.

No one really wants to see Pixelfed fail (well there are probably some), but on the whole I think we all want this to work. It's the makings of a great product.

Important issues, like the one raised here in the original toot can't go unfixed and ignored. The point of the fedi is to be open (and supportive), trusting, and honest with user data.