@bascule @matthew_d_green The WebCrypto group has a (TOTALLY INSANE) goal of legacy crypto compat.
-
-
-
@tqbf@matthew_d_green I was told the goal of WebCrypto was to build a low level API other libs could consume. This example is not that o_O -
@bascule@matthew_d_green No, potential for building on top is a “feature” but definitely not “the goal”. The goal is compat. -
@tqbf@matthew_d_green because backwards compatibility with shitty crypto is so worthwhile -
@bascule@matthew_d_green They are doing it so browsers can supplant more native code, not to make crypto better. -
@tqbf@matthew_d_green seems bad
End of conversation
New conversation -
-
-
@bascule What do you want instead? Other SSA? EC? /c@matthew_d_green -
@nahi mostly I want them to define a crypto API that doesn't repeat the mistakes of every other crypto API /cc@tqbf@matthew_d_green -
@bascule Seems a different topic but I agree on it. Crypto agility makes things hard though. /c@tqbf@matthew_d_green
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.