Quote:
Originally Posted by cerulean
Thank you for the information! BlurHash looks interesting, but I think since that solution is designed to send both the image and the blurhash in one payload for lazy loading purposes, it probably wouldn't work to prevent legal concerns.
I may look at using BlurHash for other things though. GD and Imagick blurring is really efficient, but if this is more efficient, it might be nice to integrate with some of the apps and transcoders I build.
|
BlurHash string is calculated for each image, and you need to store it. It's basically a tiny image derived from the original image, that can easily be delivered inline (inside HTML code).
What you can do with your code is only sending the BlurHash string, without the full image, until the user is permited to access the content.
Intended purpose for BlurHash is to HTML load inline (tiny) images for lazy loading.
But if you "break" the process, and deliver only hash strings, you can get an effectively blurred images based on the original ones, without actually sending the original images. Which is totally law compliant, and allows you to avoid "duplicating" the original images by blurring them. Which saves disk space.