BlurHash: Algorithm to generate compact representation of an image placeholder

Re:BlurHash: Algorithm to generate compact representation of... by bausano_michael on Thursday February 20, 2020 @09:24AM (#22375244)

I quite like that idea. Maybe you could run base64/base32 on the blurhash. That brings two potential issues I could think of. Is the size of the result less than filesystem max file name length? And what about collisions where two slightly different images have the same blurhash?

[ Parent | on HN ]

Re:BlurHash: Algorithm to generate compact representation of... by lvh on Thursday February 20, 2020 @09:33AM (#22375307)

As I mentioned upthread: none of those are disallowed on common server platforms, but ironically canonical Base64 _will actually_ break, and it'll break rarely enough that you're likely to miss it in testing! (The last character in canonical Base64, for symbol 63b10, is /, which is disallowed on (*nix) filesystems and does not occur in the native BlurHash dictionary. Unless you're suggesting encoding the encoded format, I guess.)

[ Parent | on HN ]