@bascule “CFRG: You thought arguments over elliptic curves were tedious, we can out do you”
-
-
-
@nzkoz let's talk about endianness, round 4294962795 -
@bascule I look forward to the discussion ending, then someone else piping up with “can we talk about curves with > 128 bit security level” -
@nzkoz Ed448-Goldilocks was picked as a high security curve (224-bit => 256+-bit security depending on how you define terms) -
@bascule WHAT ABOUT TWIST SECURITY!?!! (I can’t remember any specifics of that ridiculous drawn out thread) -
@nzkoz Ed448-Goldilocks passes all of the "SafeCurves" security tests according to@hashbreaker: http://safecurves.cr.yp.to/ -
@bascule@hashbreaker so wtf took like 1230498 years to discuss?
End of conversation
New conversation -
-
-
@bascule Oh FFS. Protocol Buffers and Cap'n Proto are both little-endian protocols, because LITTLE-ENDIAN IS CORRECT GODDAMMIT. -
@KentonVarda if we do a straw poll of running CPUs, little endian won by a landslide
End of conversation
New conversation -
-
-
-
@ErrataRob@bascule@jedisct1 big endian FTW. -
@matthew_d_green@ErrataRob@bascule@jedisct1 We all know that middle endian (or PDP endian) is superior ;)
End of conversation
New conversation -
-
-
@bascule let's design a cpu with byte order dependent on byte value!Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@bascule unskew the CFRG polls! -
@damienmiller@bascule big endian is just... nicer. You kids are ruining the aesthetics of IETF's beautiful protocols. - 1 more reply
New conversation -
-
-
@bascule I thought the whole point of standardizing network byte order is to prevent this kind of ridiculous dispute. What else is IETF for?Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@bascule@damienmiller I never sausage a factory.Thanks. 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.