I think it is fair to say that Synapse is more than production ready. Admittedly it can be hard to admin out of the box for smaller scale instances and we intend to improve on that experience over the coming months. Alternatively, hosting options are available[3].
After a hiatus, Dendrite is under active development and making rapid progress. It is an alpha release at the moment and not yet ready for production settings, but a beta release is coming soon.
[1] https://matrix.org/blog/2018/04/26/matrix-and-riot-confirmed... [2] https://sifted.eu/articles/element-germany-deal/ [3] https://matrix.org/hosting/
But i dont need to federate and use it more as Slack and it just keeps getting better.
I strongly suspect you’re thinking of a separate issue: the need to automatically expire old history and reclaim disk space in general, which was fixed a while back, as per https://github.com/matrix-org/synapse/blob/master/docs/messa...
I used to have more complaints about matrix clients, especially on Android, but things got much better recently.
As a bonus, it helps to support the devs too.
I totally agree that more people should look into managed hosting, though.
In other words, it’s critical that folks use the managed hosting in order to be sustainable, otherwise we’re just burning fossil fuel, as it were.
In any case, I would be surprised that Element relies on getting significant part of their revenue from the SaaS. Isn't p2p-matrix going to cannibalize that market? I could swear that the strategy for you would be to chase the enterprise/government market and let p2p-matrix as an alternative for network effects and/or those who don't want to pay and prefer to manage things themselves.
So we expect revenue from SaaS, where plain TCO says it’s cheaper to get us to host your data than pay in-house people to sysadmin it for you. It’s still your DNS and your keys, and we provide db snapshots if you want, so it really is just outsourced hosting. There is definitely a market for this, as well as separately providing support for massive on premise deployments.
P2P then drives both by network effects. It effectively becomes the default free-for-all platform - but anyone who actually wants a serious home for their data (e.g. any business) will want to find a server, whether that’s selfhost or SaaS.
I'm especially curious about the effects individually and in aggregate; I.E. if everyone did what I do.
Donations go to the Matrix.org Foundation and help pay for core team dev, but also are really useful for pointing bigger donors at to say “look, we get $4K/month on Patreon + Liberapay etc; this shows we are a good project to back; how about you match it?”
Buying hosting from Element however also funnels back to fund core Matrix dev - because almost all of Element’s work is donated (unilaterally, in an asset lock) to the Matrix.org Foundation. In other words, anything an Element employee commits into https://github.com/matrix-org automatically becomes the copyright assigned to the Foundation. This also has the separate multiplying factor that the more evidence there is to run a sustainable SaaS business on Matrix, the easier it is for Element to raise funds and keep going - and thus continue to support the core Matrix dev.
Sorry it’s so complicated, but funding FOSS is fiddly (as Mozilla demonstrates...)
P.S. thank you for donating!!
If the development of Matrix is somewhat secured and if Matthew and the team has already been compensated for their work, I'd rather support other players than concentrating it further on Matthew's hands.
That said, folks should absolutely donate to non-core-team Matrix projects like Conduit or Nheko or Dimension etc too, to support the hetrogenity of the ecosystem and keep it healthy and balanced. And once Element is sustainable (and by extension the Matrix.org Foundation funding is stable), the balance should shift even further towards ensuring the rest of the ecosystem is successful.
(Dendrite is also not inherently multiprocess - you can run it either in monolith or polylith mode).