↳
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.
@prologic@twtxt.net With respect, a client can not identify whether an edit took place. Not unless that same client witnessed both the original twt and the edited one. This won’t be the case if a person you’re following is joining a thread started by people you aren’t following after the first twt of that thread has already been modified. Or if you’re knocked offline by a multi-hour power outage that spans then entire time window between a twt getting uploaded and modified.