It's a really exciting project and I hope other phone manufacturers integrate some of those ideas.
I'm a little bit worried that their "Chatty" messaging app[2] (which is what the default Matrix client will be) is based on libpurple -- which is a library that has a pretty gnarly history of security issues[3]. It is using a plugin that the Matrix developers wrote[4], which I trust more -- but I'm still queasy about it.
I'm currently working on a Matrix-Signal bridge so I can continue using Signal once I switch to it (it won't have a native Signal app out-of-the-gate and I don't really want to run an Android emulator).
[1]: https://puri.sm/posts/massive-progress-exact-cpu-selected-mi... [2]: https://source.puri.sm/Librem5/chatty [3]: https://motherboard.vice.com/en_us/article/qkve5v/secure-mes... [4]: https://github.com/matrix-org/purple-matrix
And the microphones, please :)
https://www.apple.com/mac/docs/Apple_T2_Security_Chip_Overvi...
All Mac notebooks with the Apple T2 Security Chip feature a hardware disconnect that ensures the microphone is disabled whenever the lid is closed. On 13-inch MacBook Pro and MacBook Air computers with the T2 chip, this disconnect is implemented in hardware alone, and prevents any software—even with root or kernel privileges in macOS, and even the software on the T2 chip—from engaging the microphone when the lid is closed. (The camera is not disconnected in hardware because its field of view is completely obstructed with the lid closed.)
I highly doubt Apple will ever implement a basic hardware switch, because of it's dead-simple nature. I find it highly annoying that Apple at times is like a German car manufacturer that likes to over-engineer shit.
Being a nightly build could be a very plausible reason for this.