![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://beehaw.org/pictrs/image/c0e83ceb-b7e5-41b4-9b76-bfd152dd8d00.png)
0·
1 year agoLooks like the client isn’t, but they do offer a simple-way to self-host the backend (looks like it’s “just” a matrix server and a bunch of bridges) and then you can use any open-source matrix client to connect to that. Seems like a pretty good balance of a way to make money and the guts being open enough that one could move if the client/company goes side-ways, while contributing a lot to the open-source community.
Technically that wasn’t the initial entrypoint, paraphrasing from https://mastodon.social/@AndresFreundTec/112180406142695845 :
It started with ssh using unreasonably much cpu which interfered with benchmarks. Then profiling showed that cpu time being spent in lzma, without being attributable to anything. And he remembered earlier valgrind issues. These valgrind issues only came up because he set some build flag he doesn’t even remember anymore why it is set. On top he ran all of this on debian unstable to catch (unrelated) issues early. Any of these factors missing, he wouldn’t have caught it. All of this is so nuts.