@bascule Seems like it would be simple enough to generate a long random nonce and store it with the message by default.
-
-
@bascule Ah nice. And if you want reorder/replay protection, are sequential integers ok as nonces? (Assuming you have an atomic counter) -
@martinkl we've been looking at supporting RFC 5116-style nonces too, which are (partly) monotonic: https://tools.ietf.org/html/rfc5116#page-9 … -
@bascule How about a combination of timestamp + device ID + counter? Also approx monotonic, and enables TTL-based expiry. -
@martinkl will probably just follow RFC 5116's recommendations *shrug* -
@bascule Fair enough -
@martinkl just read your article on valuation caps from awhile ago. excellent read, thank you!
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.