[unbolted3032]

It’s a shame. There was a brief moment where there was lots of velocity on the “MSC”s as they call them - protocol features. The reference server implementations would be updated quickly, and Element would follow suit. It was exciting to follow and I would look forward to the new features hitting the clients every month or so.

I feel like that’s completely stopped.

For example, I’m still waiting for reasonable documentation to be published about how to deploy and use Element Call, which has apparently been generally available for over a year.

[ekianjo]

They had to fire a lot of devs and now they are busy re-building a new Element X client for mobile that has a 10th of the features of the older one. If you want to look for mismanagement this is a good case study.

[Arathorn]

Thanks for all the positive vibes & hugops folks :D

Fwiw, the DB isn't corrupted - the database 2ndary dropped its RAID array on having new disks added (the hw raid controller incorrectly added them into the array, breaking it)... and a few hours later we lost the primary db too. The outage is caused by the time taken to restore & rebuild a 55T db from nightly snapshot.

In terms of lack of documentation for running Element Call: i published a tutorial & video run-through myself back in November: https://element.io/blog/experimenting-with-matrix-2-0-using-... and https://github.com/element-hq/element-docker-demo and https://youtu.be/6iMi5BiQcoI. Or you could just run it via Element Server Suite: https://element.io/server-suite/community

In terms of "Element X has a 10th of the functionality of classic Element" - with respect, this is bullshit. The only features folks complain about missing are Threads & Spaces, both of which are have implementations behind feature flags and will land shortly. In all other respects Element X is a wild improvement over classic Element.

Fwiw, there's another HN thread on this over at https://news.ycombinator.com/item?id=45107696

[ducktective]

Keep up the good work! There are satisfied but silent, Matrix users too.

[ThePowerOfFuet]

>the database 2ndary dropped its RAID array on having new disks added (the hw raid controller incorrectly added them into the array, breaking it)

You really, truly should look at ZFS.

[q3k]

> hw raid controller

... oof.

[ThePowerOfFuet]

Yep, that was my reaction too.

[wind12]

> They had to fire a lot of devs

What happened and why? Any pointers to read more on this?

[Arathorn]

https://m.youtube.com/watch?v=lkCKhP1jxdk&t=741 is firsthand info