Thank you - the thanks is hugely appreciated; E2EE-by-default has been a never-ending project with a lot of moving parts, and given the end result is basically invisible if successful, and the enormous blogpost is a bit indigestible, it's really nice to hear the encouragement and positive feedback. Thank you for believing in Matrix and supporting us!!
You and your team deserve it and much more!! Actually love how you put things in one place. The API documentation is a good example. Rather not have to search around and go from page-to-page searching for things; feels like a feature to me;)
This is what I'm talking about. Responsive communication from all levels. And not just because it's HN and "like we gotta look good now because we announced something." Responsiveness has be consistent and the baseline throughout my involvement with Matrix as an organization and a community.
Also really appreciated the full workup on the latest release. Know with developing like 15+ applications is hard enough, getting information out to the community in a thorough way is such a heavy burden on top of all the other work going on.
Few questions -- Any timeline on when:
* account-password/backup-key-passphrase will be consolidated (end-of-summer possibly -- fingers crossed);
* ‘trust on first use’ (TOFU) will be integrated;
Think those two features will be important for improving UX.
Also, encrypted search via Seshat: Simply, YESSS!!
So, cryptographic login (i.e. consolidating login password and recovery passphrase) is a fairly challenging task, which is why we descoped it from E2EE-by-default. For instance, we need to make sure we don't break clients which don't want to do cryptographic login (e.g. Riot single-sign-on, or those who don't support E2EE). We also need to make sure that users can reset and rotate their passwords without losing their E2EE history. We'd also have to completely rewrite the registration/login process in Riot (again). We can't commit to timings on it, but based on the feedback from E2EE-by-default it'll be pretty high on the todo list.
TOFU is much easier, and hopefully we can sort it out as part of incremental fixes having now gone live. We almost snuck it in before release, but it'd have pushed things out even further. https://github.com/vector-im/riot-web/issues/12719 is the bug to follow here.
But yup, these will be the difference between today's 1.0 and an (even) better UX.
