## 13.78126

there’s apparently technical guidelines^{1} that talk about turning random bits into random numbers between 0 and something other than powers of two.
unfortunately it’s lacking a bit of nuance.

there’s apparently technical guidelines^{1} that talk about turning random bits into random numbers between 0 and something other than powers of two.
unfortunately it’s lacking a bit of nuance.

i’ve been using a pair of (relatively) cheap ar glasses as my primary display for a few weeks. overall i like it a lot, still need to get lens inserts to correct my elliptical (and a little interpupiary distance difference). but it’s only 1080p per eye, so of course i’m looking at how to build something better. which end me up looking at datasheets for ti’s mems display chips…

i’ve been wanting a good way to migrate signature keys in converge. ideally a migrating key pair that:

- signatures can be verified correct with merely the signing public key
- the migrating secret cannot be derived from the signing secret key
- even if the migrating public key is known

in cryptography, we often require domain separation for different uses of the same primitives. roughly, this means ensuring that the inputs to a primitive for different purposes cannot overlap. so there are no instances where you can lift a value from one part of the protocol and use it in another.

i’ve been thinking about data confusion - interpreting the same pile of bytes as different types.