↳
In-reply-to
»
So, uh, did anyone but me notice that the last character of a twt hash is always either an
⤋ Read More
a or a q? Which is the natural consequence of taking the last digit in the base32 representation of a 256-bit hash -- 256 is not evenly divisible by 5 ! That final character is made up of one bit of actual information and 4 bits of padding.
Speaking only for myself, I’d like threading to work in a way that lets me keep using my flaky home internet connection, rather than spend money on a VPS in some datacenter with a reliable connection.