News for hackers. Stuff that matters.
Re:Cross-signing and end-to-end encryption by default by badrabbit on Thursday May 07, 2020 @06:52PM (#23109318)
Usable for technical people,but as they note at the end of the blog post, they have ways to go with respect to first time user experience.

I tried getting a team of tech savvy people to use it for backup encrypted comms, the UX was horrid, the key verification just didn't work at the time. Hopefully this is fixed.

I am hoping a commercial product comes out of this,so they have proper QA and UAT. The FOSS approach of filing an issue/bug when basic things fail does not translate well to a generic audience. The protocol and Riot are actually decent,but I think the UX has yet to catch up with the rich feature set.

Both Signal and Slack just worked. Slack has great UX, Signal is mediocre but from a security perspective, many things are non-obvious which to me feels like a dark pattern of insecurity,Riot maybe more painful but fails in more obvious ways.

Re:Cross-signing and end-to-end encryption by default by Arathorn on Thursday May 07, 2020 @08:13PM (#23109898)
> the UX was horrid, the key verification just didn't work at the time. Hopefully this is fixed.

This is what we've tried to fix in this release :) Meanwhile, as you note, first time user experience is our single biggest project now e2ee-by-default is shipped.