2 ms·
interesting blog post as always :) > This observation leads to two possible interpretations (both bad): - The Version 2 code is an unfinished experiment that
by throawayonthe 8mo ago
interesting blog post as always :)
> This observation leads to two possible interpretations (both bad):
- The Version 2 code is an unfinished experiment that should’ve been relegated to a development branch rather than dumped into the production version that real clients use today.
- The Version 2 code is intended to be used today, but Matrix is consistently incapable of designing protocols that resist even the laziest of active attackers.
i'm curious, could another interpretation be something like staggered rollout of v2? like, making sure clients already have the v2 code path for when other clients start disabling v1 idk
- tcfhgj 8mo agoI git blamed it and if I read it correctly it seems like they even use version 1 as a default, because that's the actually spec compliant option: https://github.com/matrix-org/vodozemac/pull/287 https://github.com/matrix-org/vodozemac/pull/287