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.
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 "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, 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