@dakami @matthew_d_green @maradydd language chauvinism is irrelevant. 99.9% of programmers will use an API like this incorrectly
-
-
Replying to @bascule
@bascule@matthew_d_green@maradydd The point is to create a more useful abstraction than pile-o-ciphers, not to care about C/JS2 replies 0 retweets 0 likes -
Replying to @dakami
@dakami@matthew_d_green@maradydd in other words, it should work like NaCl or Keyczar. Current spec is the OpenSSL debacle all over again2 replies 0 retweets 0 likes -
Replying to @bascule
@bascule@matthew_d_green@maradydd You think you get to tell devs what to do. You don't. You can only be useful to them.1 reply 0 retweets 0 likes -
Replying to @dakami
@dakami@matthew_d_green@maradydd I'm saying the spec should have expert cryptographers to make choices so developers don't have to1 reply 0 retweets 0 likes -
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
@dakami @maradydd @matthew_d_green 99.9% of developers don't understand crypto. To build secure systems, it needs to be as easy as GPG
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.