Finally I propose that we increase the Twt Hash length from 7 to 12 and use the first 12 characters of the base32 encoded blake2b hash. This will solve two problems, the fact that all hashes today either end in q or a (oops) ๐Ÿ˜… And increasing the Twt Hash size will ensure that we never run into the chance of collision for ions to come. Chances of a 50% collision with 64 bits / 12 characters is roughly ~12.44B Twts. That ought to be enough! โ€“ I also propose that we modify all our clients and make this change from the 1st July 2025, which will be Yarn.socialโ€™s 5th birthday and 5 years since I started this whole project and endeavour! ๐Ÿ˜ฑ #Twtxt #Update

โค‹ Read More

July 1st. 63 days from now to implement a backward-incompatible change, apparently not open to other ideas like replacing blake with SHA, or discussing implementation challenges for other languages and platforms.
Finally just closing #18, #19 and #20 without starting a proper discussion and ignoring a โ€˜micro consensusโ€™ feelsโ€ฆ not right.

I donโ€™t know what to think rather than letting it rest (May will be busy here) and focus on other stuff in the future.

twt-hash-v2.md#implementation-timeline

โค‹ Read More

Participate

Login or Register to join in on this yarn.