lol we've reached peak webdev, gents. ;)
lol we've reached peak webdev, gents. ;)
@wyatt @kawa There have been a few attempts at "lossy PNG". One method, anticipated by the standard, involves reducing colors in a continuous-tone image to store it in indexed mode. The other involves adjusting pixels of 24-bit images to be better predicted by PNG's line filter, giving more zero bytes for DEFLATE to use
Indexed: https://pngquant.org/
Blurizer: https://github.com/kornelski/mediancut-posterizer/tree/blurizer
Gotta say, for $20/mo, this is pretty flipping incredible!
Uhhh, sβsure, #Thunderbird. You go right on ahead and reclaim those 218 GB. π€·ββοΈ
It's really something that my e-reader has better and more usable scrollbars than most desktop interfaces (Windows, MacOS, and Gnome). :/
The scrollbar is thin, but the grabbable region is large (kind of like the default in KDE), and easy to manipulate directly with your finger. This is actually better than #iOS' implementation, and many #Android apps.
If anyone's curious why I'm always doing the little #LossyPNG dance, it's because you can get some crazy good compression sacrificing color depth, instead of using a traditional lossy algorithm which gives you good compression by sacrificing detail:
tmp $ ll kate*
-rw-rw-r-- 1 rld rld 124,117 Feb 23 12:51 kate-kwrite1.png
-rw-rw-r-- 1 rld rld 23,710 Feb 23 12:51 kate-kwrite2.png
-rw-rw-r-- 1 rld rld 19,936 Feb 23 12:54 kate-kwrite3.png
-rw-rw-r-- 1 rld rld 18,572 Feb 23 12:55 kate-kwrite4.png
186335 total
tmp $ colors kate*
kate-kwrite1.png (unknown)
kate-kwrite2.png 16
kate-kwrite3.png 9
kate-kwrite4.png 8
(kate-kwrite1.png was the original (truecolor) screenshot)
(kate-kwrite2.png was automatically reduced to 16 colors by ImageMagic)
(kate-kwrite3.png was reduced to 9 colors by hand-picking dominant colors in GIMP)
(kate-kwrite4.png was reduced to 8 colors by hand-picking dominant colors in GIMP)