Matrix proponents would do well to learn from what is happening to Firefox and Mozilla.
Element do 90% of the development in the Matrix ecosystem - including the only server that can run at scale (I wont say "work") and the only homeserver designed to replace it (not production ready).
If Element were to come on hard times (as they have in the past, with near disastrous results), Matrix will simply fold.
@kline What do you suggest as alternative for a potentially struggling company? No company?
So I have seen tons of really brilliant projects that were abandoned simply because the developer wasn't able to continue working like a slave to satisfy continuous stream of demands from bastard users who didn't give a fuck to even say "thanks", not to mention donate $2 pm to a project they use and benefit from on daily basis.
Therefore, whenever I see a project I use and like and don't want it to disappear, I just start donating to it, using any means available.
@kravietz @anornymorse @arjen I think what would be better is to build a community of developers who can scratch their own itch and spread the load of bastard users.
Predicating your project on getting big enough to make cash quick is a bad strategy.
A good case study is OpenSSL project which was developed initially by one guy (EAY) then taken over by others and, having a very permissive license, was immediately commercialised by some companies, and used by literally everyone on the Internet, while the developers were funded in a typical trickle-down model like "oh we earned $1m on your code, but our shareholders won't approve $1k for you if you publish your code for free, but hey, here's $100 donation!"
@kravietz @anornymorse @arjen this whole discussion and the original post is about building resilience of software projects. Being profitable but still super centralised on one individual or group is the issue. Some people try and fix this with money (as someone is less likely to leave when they're being paid), but it's never going to get fixed unless you dampen the bus factor.
You're raising absolutely valid point about project management but it's a bit of a separate issue.
A project like Matrix or OpenSSL is not only code but also issue management, project management, security, documentation, user support, website, business logic maintenance & updates etc etc. Projects like Nmap, Nessus or Suricata also require very frequent rule updates. All that tends to be extremely boring and routine work.
Volunteers tend to lose interest in these.
@kravietz @anornymorse @arjen alright, but I think that these issues are completely unrelated to Matrix being centralised and are probably best discussed in a thread of their own.
I don't think that the solution proposed here ( https://social.privacytools.io/@kravietz/104680879548972793 ) is a practical one that actually addresses the issue this thread is about.