You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think we could optimize the emoji used,
there are some sets of emoji that are sort of similar, like multilpe different sorts of arrows,
one hump and two hump camels, several different buildings, etc, etc.
Also lots of clocks, it is probably easier to remember "clock" than 6:30
I've been thinking about actually experimentally testing this with a psychological experiment where people rember hashes encoded as hex, base64, and emoji, and detect how well they detect partial collisions by eye.
The text was updated successfully, but these errors were encountered:
I think we could optimize the emoji used,
there are some sets of emoji that are sort of similar, like multilpe
different sorts of arrows,
one hump and two hump camels, several different buildings, etc, etc.
Also lots of clocks, it is probably easier to remember "clock" than 6:30
I've been thinking about actually experimentally testing this with a
psychological experiment where people rember hashes encoded as hex, base64,
and emoji, and detect how well they detect partial collisions by eye.
—
Reply to this email directly or view it on GitHub #5.
I think we could optimize the emoji used,
there are some sets of emoji that are sort of similar, like multilpe different sorts of arrows,
one hump and two hump camels, several different buildings, etc, etc.
Also lots of clocks, it is probably easier to remember "clock" than 6:30
I've been thinking about actually experimentally testing this with a psychological experiment where people rember hashes encoded as hex, base64, and emoji, and detect how well they detect partial collisions by eye.
The text was updated successfully, but these errors were encountered: