@npmccallum i think it's good and i have the Android app, which is functional
@npmccallum i do remember us having issues with encryption which was optional
from what i remember, we had to turn encryption off in the room
Anyone with the iOS app have any issues?
as far as i know, the iOS version and Android version are very similar (if not essentially the same) as built from the same SDK
otherwise, i'd say that @whitebrandy's comments are spot on
encryption has been a work in progress for a while
it's progressed leaps and bounds in the past couple years however, to the point we are weeks/month(s) away from the matrix team flipping the switch and enabling E2E encryption on all new 1-1 chats
it's always going to be a choice on rooms, as some rooms are small and some big, and it makes little sense in what are public rooms to add the overhead of encrypting each message for every device of every user in a room. If it's public, it probably doesn't need encryption (though it can still be enabled)
@mbestavros RiotX has some nice new things, like swiping on a message to reply to that message, but it's missing other things like, hmm, answering an audio call :)
Hi, I joined your daily meeting yesterday. Thanks for speaking with me! I wasn't able to find any documentation online about how to get started with any SME instances. IBM casually but vaguely mentioned earlier this month that they will start to support this, but I wasn't able to find more detailed information. Is it possible to access such instances via Red Hat services? Is SME only supported on Linux? I understand that you're developing an interface to help people make use of memory encryption. Do you have any documentation explaining what your product will support? Thanks again :)
@jmstoller_gitlab We aren't using AMD SME. We're using AMD SEV.
(There is currently a lot of confusion around these technologies.)
Ah thanks @npmccallum , I actually meant SME or SEV. We're interested in both!
SEV is basically a superset of SME plus other features.