thats a very fair point, I had not seen anyone else make this one But the problem is that in this case, this functionality was entirely undocumented. I dont think it was intended for programmers.

Now if the firmware was open source, people would have gotten to know about this much sooner even if not documented. Also such functionality should ideally be gated somehow through some auth mechanism.

Also just like how the linux kernel allows decades old devices to be at the very least patched for security risks, open firmware would allow users of this chip to patch it themselves for bugs, security issues.

We really should be pushing for fully open source stack (firmware, os) in all iot devices. They are not very complicated so this should be entirely possible. Probably will need a EU law though.

depending on which client you use, the ui can be very discord-like (this is cinny): https://raw.githubusercontent.com/cinnyapp/cinny-site/main/assets/preview2-light.png

Also matrix has calls (at least element does), though not sure about screen share. And since when was discord e2e?

I ll admit matrix was for a long time really slow but matrix 2.0 largely solves this and other usability issues. Calls and screen share are still not standardized but its all being worked on.

With matrix, its not just about building one app, its about building a decentralized ecosystem all connected by the matrix protocol. So things tend to take more time.