@dakami @matthew_d_green @maradydd I'm saying the spec should have expert cryptographers to make choices so developers don't have to
-
-
Replying to @bascule
@bascule@matthew_d_green@maradydd No, see, you're saying the only thing that should be fast, is what you like.1 reply 0 retweets 0 likes -
Replying to @dakami
@dakami@maradydd *I* don't want to be making those decisions. I want someone like@matthew_d_green making them for me.4 replies 0 retweets 0 likes -
Replying to @bascule
@bascule@maradydd@matthew_d_green We can choose to make existing cryptosystems fast, or only new ones (written to NaCL)1 reply 0 retweets 0 likes -
Replying to @dakami
@dakami@maradydd@matthew_d_green you can do both so long as the API clearly separates what to use for new projects versus legacy interop1 reply 0 retweets 0 likes -
Replying to @bascule
@bascule@maradydd@matthew_d_green Lies we tell ourselves. Make useful things for devs, then make them fast.2 replies 0 retweets 0 likes -
Replying to @dakami
@dakami@bascule@maradydd@matthew_d_green everything can be fast, but the API design should aid the decision-making process1 reply 0 retweets 0 likes -
Replying to @bascule
@bascule@maradydd@matthew_d_green devs can tell when you're cheating. Make the awesome useful API that gets adoption.3 replies 0 retweets 0 likes -
Replying to @dakami
@dakami@maradydd@matthew_d_green WebCrypto could be that if they clearly prescribed what users *should* be using in new apps2 replies 0 retweets 0 likes -
Replying to @bascule
@bascule@maradydd@matthew_d_green Because, we've been full of shit so so so many times2 replies 0 retweets 0 likes
@dakami @maradydd someone like @matthew_d_green may be full of shit due to unforeseen attacks but I trust his opinions much more than my own
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.