[ an / aw / cr / fi ] [ ra ] [ au / ga / he / sp ]

/aw/ - AwsumChan Meta

Discussion of AwsumChan itself.
Name
Email
Subject
Comment
Verification
File
Password (For file deletion.)

File: 1580891817133.png (6.03 KB, 186x66, WebP.png)

 No.211

So far iOS is our last major obstacle (screw IE lol).

Is there any polyfill usable on Tinyboard (i.e. something to easily add to $config['additional_javascript'] or $config['url_additional_javascript']), to make pics viewable on iOS browsers?

Yes I know about pagespeed and the likes. I don't like keeping extra sets of converted images. It defeats the purpose of saving space.

 No.212

Regardless of above,
when I use ImageMagick to convert a WebP file to a JPG thumbnail,
the result is fine,
but IM feels obliged to also write these to stderr:

>Decoded /tmp/magick-**. Dimensions: * x *** . Format: lossy. Now saving…

>Saved file /tmp/magick-****

Somehow IM needs to make temp files only when dealing with WebP format.
That's fine.
But Tinyboard's image.php (line 376) treats the stderr message as a blocking error.
Can you fix this?

 No.213

>>212
I'll look into it. I had WebP on the agenda and it was implemented for a while, but I was noticing a lot of distros were behind on the support for it. But that should not be a concern now.

 No.214

>>212
>>213
Plain GD (unless very ancient PHP) already works well with WebP and thumbnailing though. It's just config.php suggests IM and GM are still better at this job for some reason.

GD thumbnail functions are more hardcoded in image.php thus less configurable. I could modify it myself but I think it's better to suggest upstream changes rather than fiddling alone.

For example, what do you think about adding imageinterlace() for making progressive (smaller) JPG thumbnails, and imagejpeg() defaulting to about 75 quality?

 No.216

>>214
PHP 7.2 didn't have support for WebP most of it's release schedule. But since most distributions now have forced an upgrade to 7.3 due to a vulnerability, it would make sense to implement WebP as an option finally.
As for JPEG thumbnailing options, that seems like it'd be a good idea, I'll do some tests to see the difference.

Excuse me for the seeming lack of presence, I've been really busy with ongoing events and have yet more planned through March.

 No.221

>>214
>>216
So a followup on this - turns out I never removed the code that implements WebP. All that should be necessary in order to use it is to add this to your inc/instance-config.php
$config['allowed_ext'][] = 'webp';

 No.260

>>221
As >>214 said it's for GD only.
If you configured Tinyboard to IM or GM, the stderr output still needs to be worked around.

>>211
iOS and Safari will natively support WebP next version. It's such a relief.


Also dear Circlepuller: Is there an easy option in Tinyboard, so that uploaded images are automatically converted to WebP (or any other specified format)?

 No.261

>>260

If you mean converting thumbnails:

$config['thumb_ext'] = 'webp';

As for converting original files. It doesn't, feel free to submit a PR on GitHub and I'll likely take it.

This should do it. As for the suggestion towards IM/GM, it's because it has historically been better thumbnail resizing quality and paired with Gifsicle. But yeah, GD is absolutely fine, it's just not as comprehensive has IM/GM+Gifsicle, so I still recommend it to this day unless WebP is your goal. I'll look into fixing the stderr issue unless you beat me to it in a PR.

Yeah, with increasing support for WebP I will likely switch the default thumbnailing method and other static imagery to WebP.



[Return][Go to top] [Catalog] [Post a Reply]
Delete Post [ ]
[ an / aw / cr / fi ] [ ra ] [ au / ga / he / sp ]