That is totally the right question. Everyone is comfortably at their layer in the stack. We need more programmers with your mindset (and skill). Thanks for keeping at it and show us.
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
The go language implementation has benchmarks. Here's a link to the test file that contains the benchmarks. Best I can do on phone. https://cs.opensource.google/go/x/crypto/+/0ba0e8f0:chacha20/chacha_test.go …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
From the perspective of a user with only the standardized options to choose from: it’s never the throughput/latency bottleneck on servers. On the (often) ARM clients it is more significant in profiles, but was at least at one point, the best choice: https://www.imperialviolet.org/2014/02/27/tlssymmetriccrypto.html …
-
I came here to say the same. ARM clients is where I've seen performance mentioned. And for full disk encryption, they even reduce the number of rounds. https://tosc.iacr.org/index.php/ToSC/article/view/7360 …
End of conversation
New conversation -
-
-
In general no, I don’t think many people are paying attention to that, they’re just using whatever ships with what they got. There is some work at http://bench.cr.yp.to/impl-stream/chacha20.html … but it’s not bleeding edge
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I would think
@programmingart would care -
- Show replies
New conversation -
-
-
Because browsers can't handle 6+ WebRTC streams SFU proxying is important, but InsertableStreams lets us mix/encode/encrypt so we mix 3 participants "beneath" me. My mixed stream gets mixed by someone "above" me. Server ideally least work, just bandwidth relay.
@qxipThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.