> There is a possibility of collisions in the future, we can use the reserved flags as a nonce for known collisions if this ever comes up. This is a ticking ti

> There is a possibility of collisions in the future, we can use the reserved flags as a nonce for known collisions if this ever comes up. This is a ticking time bomb. Good luck getting folks using this standard to implement this properly when this eventually happens. If this is the contingency for a collision, then a massive non-hash-based list of every combination was probably a better solution to begin with. Edit: On second look, I'm not sure if binmoji is working properly? The component hash lookup table seems way too short to cover even a fraction of possible combinations, and it doesn't seem like it can properly roundtrip emojis such as this diverse family emoji: https://apps.timwhitlock.info/unicode/inspect?s=%F0%9F%91%A8%F0%9F%8F%BF%E2%80%8D%F0%9F%91%A9%F0%9F%8F%BE%E2%80%8D%F0%9F%91%A7%F0%9F%8F%BD%E2%80%8D%F0%9F%91%A6%F0%9F%8F%BC https://apps.timwhitlock.info/unicode/inspect?s=%F0%9F%91%A8...