Earlier quoted context omitted.
The solution is non profits or open protocols. Internet Archive. Let’s Encrypt. Signal. Peertube. Jitsi. AT Proto. (not an exhaustive list) Competition is not the way out, but building public goods through corporate entity structures that are protected from the usual capitalist forms of acquisition (B Corps are not required to maximize value, non profits can be made almost impossible to acquire through incorporation…
Non-profits and open protocols dont do jack squat when capitalists surround those things. See: Mozilla Firefox and WHATWG The latter particularly being membered by all the big corpos and introducing, controlling, and deprecating standards as they see fit and regardless of pushback from the public.
Marketing is a way smaller reason than many people imagine—it’s mostly usability. See the nearly immediate mastodon mass-exodus after getting millions of people to give it a shot. Yet most people that use signal probably don’t even know what open source means. Try to find a full-time professional photographer or designer that’s never tried Gimp, but immediately abandoned it. (The project is making a serious concerted effort to turn it around though! I think a lot of it comes down to who makes product decisions.
For open protocols, engineers with experience deploying things in real-world situations should obviously call the shots. We don’t need bean counters unilaterally deciding about things like Pocket integration, or shoving chatbot features into every crevice so they can look cool on LinkedIn.
But the people steering end-user-facing tool projects should be product people who are primarily interested in solving tangible real-world problems. Technical people often prioritize technical consistency or ease of implementation over usability, and incorrectly assume that nontechnical end users will be fine with it — they just need to RTFM Amiright? Technical people also tend to overestimate their ability to reason about design problems the same way that some designer might vibe code a few things, read a book about Python, think they’re basically a web developer, and then start saying confidently incorrect things about technical topics.
Alas, product managers and designers are not an easy fit into regular FOSS workflows. I’m sure someone with good organizational management skills could totally devise a FOSS project structure that would do the trick.