construct VS Synapse

If that's the bar, then mobile Linux is simultaneously very fucking far, and dramatically closer than most people might think.

As far as messaging apps, they're all technically there - the best kind of there for the crowd that this would interest. Spinning up a Matrix server means maybe a days work for this crowd, which allows (and I currently use it for) Whatsapp, Signal, Telegram, and more. Even better, due to constant improvements by Matrix, the server is only getting lighter and your options more varied with things like Construct [0].

Email is there - one only really needs to ensure geary is set to scale to the phone screen. As far as gMail, I'd question what the overlap is between "Privacy conscious enough to use a Pinephone" and "Uses gMail instead of anything IMAP".

That only leaves navigation and social media. For the former, I've used the mobile site in-browser on my Android phone that the Google Maps app was too heavy for. And for both on the Pinephone, especially the pro, Waydroid [1] is getting closer to closing the gap.

To be honest, I could see it being mainstream for geeks within two years. Though that's unlikely what you meant by mainstream - which I think we can agree is several more years away, if ever.

[0] https://github.com/matrix-construct/construct

[1] https://github.com/waydroid/waydroid

On its project GH roadmap, why then does it say:

It does - the point is that anyone can spin up their own Matrix server (or pick an existing one) and get involved; they don't have to use the fosdem.org one.

Separately, in terms of implementations: Dendrite is usable these days, albeit beta: https://matrix.org/blog/2020/10/08/dendrite-is-entering-beta, and meanwhile Synapse is stable. Conduit (https://conduit.rs) is making progress on federation (and works for simple use cases), and Construct (https://github.com/matrix-construct/construct) exists too.

What are you thinking of here? Synapse has supported purging room history since 2016: https://github.com/matrix-org/synapse/pull/911, and configurable data retention since 2019: https://github.com/matrix-org/synapse/pull/5815.

Meanwhile, Matrix has never needed the full room history to be synchronised - when a server joins a room, it typically only grabs the last 20 messages. (It does needs to grab all the key-value state about the room, although these days that happens gradually in the background).

If you're wondering why Matrix implementations are often greedy on disk space, it's because they typically cache the key-value state aggressively (storing a snapshot of it for the room on a regular basis). However, that's just an implementation quirk; folks could absolutely come up with fancier datastructures to store it more efficiently; it's just not got to the top of anyone's todo list yet - things like performance and UX are considered much more important than disk usage right now.

some context re the Matrix isses, long history apparently: https://github.com/matrix-org/synapse/issues/14481#issuecomm...

Why not Matrix? Here's one reason: it has incredibly hard-to-debug edge cases, and plenty of bugs. One of my favourites is the one where people are kicked out of your room at random, which was reported a year ago[0]. It wasn't fixed, however, because the head of the Matrix foundation (Matthew) presumably didn't like the issue being posted on Twitter.

This is honestly really disappointing behaviour from a platform owner.

[0]: https://github.com/matrix-org/synapse/issues/14481

> That doesn't make this situation any less bad to the rest of the community.

How is the community suffering here? Let's say Element adds a bunch of baller stuff to their versions over the next few months and then closes the source. Can't the community just fork the last AGPL version? You might say, "well then no one can take the AGPL fork and make their own closed-source business", but do you want them to? Even if you do, they still can with the existing Apache-licensed version, just like Element is doing right now.

You're arguing that Element will lose a lot of contributions, but TFA points out that despite being super open, the vast majority of contributions are still made by Element employees (which seems to be true [0]). It's not the case that Element is looking to monetize the (small) contributions of others, it is the case that others are looking to monetize the (huge) contributions of Element.

And besides, aren't the MSCs the core of Matrix? It's already super possible to build your own compliant client and server.

The situation is that Element needs money to keep developing the ecosystem. It would be cool if there were a big network of donors and contributions, but there isn't. You're essentially saying, "that's fine, go out of business then, and the community will keep developing the ecosystem", but that's not happening now, and it can still happen anyway with the Apache-licensed versions, which again people can still contribute to.

[0]: https://github.com/matrix-org/synapse/graphs/contributors