↳
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.
And I’d like to be able to fetch the feeds of people I don’t regularly follow on an as-needed basis, instead of having to pre-emptively discover and fetch every feed in the entire network just in case they might be relevant to a thread in the near future.