>>107166747
Hipster trash.

easier to exploit
like this site got hacked with a pdf file for crying out loud

>>107166853
What do you mean?

File: jpeglizzzzzzzz.jpg (1.86 MB, 3840x2160)

1.86 MB JPG

>>107166747
4chan doesn't even support jpegli images. Recently it was hacked because typing update pkg && upgrade pkg was very difficult for the devs. Adopting webp on 4chan is far beyond what the devs are capable of here.

Picrel was converted to a standard JPG which is why the file sizes don't match. You can find the original jpegli file here:

https://files.catbox.moe/xt5fcm.jpg

Filesize of the jpegli: 1.76 MB

When you download the image you'll get this:

Filesize of 4chan raped jpegli: 1.85 MB

>>107166918
Why is that? t. Complete technological illiterate

>>107166770
For photographic images? Kinda. I made a thread about it and it's breddy good for toon image sources. Seems a little relevant for an anime website maybe...

https://desuarchive.org/g/thread/106963313/

>>107166983
Because the people running 4chan are just as tech illiterate as you. Jpegli was created specifically to make webp obsolete.

>>107166853
source?

>>107167036
An outdated libwebp component of handling webp images allowed hax0rs to do RCE through a malicious lossless webp file. Think of it like drive by malware, you can learn more on the WikiLeaks vault 9 shit if you want.

4chan will DEFINITELY fucking up updating that libwebp component 100% guaranteed.

>>107167055
no, I meant source saying that the library of decoding webps is exploitable with proof.

otherwise you are just making things up.

>>107167055
>>107167101

>WikiLeaks vault 9
the fuck is that?
do you have a url?

>>107167101
>>107167115
I don't want to get party vanned so this is the best I can do. This exploit might be related to why 4chan won't allow jpeg images btw.

https://www.wiz.io/blog/cve-2023-4863-and-cve-2023-5217-exploited-in-the-wild

>>107167144
>jpeg
jpegli**** fucking cocksucking auto-correct piece of shit, I can't disable you motherfucker

>>107167144
interesting,
ok that was two years ago,
so naturally they fixed it right?

isn't it how it goes?
a vulnerability is discovered in some library and then devs patch it,
right?

>>107167208
You would think but 4chan is most likely running libwebp 0.0.1 alpha and they will NEVER update it until they get hacked up the ass again. So their logic must be, "uhhhhhh let's just leave it disabled forever!".

Mission accomplished

>>107166853
Skill issue.

>>107166918
>Recently it was hacked because typing update pkg && upgrade pkg was very difficult for the devs.

Consider that this would have broken everything because the 4chan source barely ran on PHP5.6, it didn't even use mysqli classes.

>Picrel was converted to a standard JPG which is why the file sizes don't match.
>Filesize of the jpegli: 1.76 MB
>Filesize of 4chan raped jpegli: 1.85 MB

4chan runs this on jpgs:

/usr/local/bin/jpegtran -copy none -outfile '$file' '$file'

so that might be why your file gets raped? I dunno. Nothing else in the source seems to point to a problem.
It's necessary to run that to remove all embedded file data, because niggers were uploading images with winrar archives embedded after the image data containing cheese pizza.

Also consider that 4chan serves files via cloudflare which do recompress the file, that's a bigger problem for a whole other heap of reasons, but it was again necessary because niggers uploaded images with cheese pizza embedded (google coomdev/pngextraembedder). And also cause it saves bandwidth.
so even though 4chan reports 1.86MB, the actual file sizes are:
xt5fcm.jpg -> 1849372
1762811920020213 -> 1852685

btw, the latest idiocy spammers try is storing encryption keys in filenames for catbox hosted cheese pizza, so expect original filenames to be removed soon as well.

>>107167235
>>107166747
webp is internet cancer though, so I hope it won't ever get supported.

it's literally google strongarming everyone via their SEO supremacy to force transcoding all lossy file data to their format. consider if your mp3 player of choice automatically transcoded everything to ogg vorbis; that's what webp is to the web.
so webp can go and get fucked as far as I'm concerned.

>>107167553
See >>107167012

Should EVERYONE be using webp? Of course not, that's stupid. 4chan is a good candidate thoughbeitism-ed-d

>>107167514
nta but i do also wonder what (and why) 4chan fucks up. i run my uploads through jpegoptim -ps --all-progressive and once they're uploaded they're balooned back by a few percent. is customized huffman stripped or something?

>>107167055
>>107167101
>>107167144
>>107167235
What makes you believe 4chan needs to decode webp files on the server in order to support them? For what specific reason would they even need to have libwebp at all in order to support the posting of webp files?
Don't talk about things you have no knowledge of NIGGER

>>107166747
I think they are using php4 and It doesn't have support for webm.

>>107167702
Because these sick fucks will embed CP in them you ding dong. So 4chan has to make extra sure a webp uploaded isn't going to get other users vanned. Did you not see the ape rapists crying about the feds not *doing their job* (ie he's admitting 4chan is understaffed)?

File: Image1.png (3 KB, 396x59)

3 KB PNG

>>107167575
No, webp should not be supported on solidarity alone. And if you want your images to be smaller, you should be supporting JPEG XL instead which is all around superior format and works better than AVIF too.

>thoughbeitism-ed-d
trip up your shill copypasta?
>run "thoughbeitism" on google
>only result is wikipedia page for "philosemitism"

oh, wow.

>>107167664
Just tested it, it's jpegtran fucking up. The jpeg data is completely different in hex.

4chan is only to blame in that it uses antiquated tools, which is to nobodies surprise given that it was written 20+ years ago and hand patched over the years with only whatever updates are needed to block glownigger cheese pizza spam.

>>107167752
There are third party services that do that. 4chan isn't processing cp on their own server, the images get sent to a glow site that contains a database of hashes and automates alerting authorities.

File: DecodeMPs_Chrome-110-S10e(...).png (26 KB, 900x556)

26 KB PNG

>>107167761
>which is all around superior format and works better than AVIF too.
Too CPU intensive but yeah this is the next "h264" of images in the next decade or so. For now webp is still better than nothing imho.

>>107167768
You say that after like a year of sinks getting posted went unnoticed. Nah jay be flicking his bean to all that nasty shit mang...

>>107167777
>muh oppressed cpu
avif is still a video iframe, gpus will produce shit results, resolution is capped so it resorts to grids. maybe tenable for doomscrolling past a bunch of thumbnails.

>>107167777
>For now webp is still better than nothing imho.

No, it is WORSE than nothing because 99.999999% of webp content online is lossy transcoded.

File: baseline (1).png (24 KB, 1200x742)

24 KB PNG

>>107167849
Yeah at fucking 4K res for the baseline bare minimum and 8K res for everything else. Also to be fair GPU AVIF encoding is going to compete with GPU JPG encoding (ie nvjpeg) so I don't think you have any idea of what you're talking about.

>"look my jpeg xl is 30% smaller! and only took 1,000 longer to encode!"

https://developer.nvidia.com/nvjpeg

>>107167901
Oh you mean like all these niggers converting JPGs to PNGs? JPG is a fucking joke because people convert them to PNGs?

>>107167921
>Oh you mean like all these niggers converting JPGs to PNGs? JPG is a fucking joke because people convert them to PNGs?
You are talking out of your ass. Almost nobody does that. Meanwhile jpg->webp is done by *every* fucking site on the internet that does even basic seo optimisation, thanks to Google actively penalising everyone not using webp. There are Wordpress plugins to automatically do it, for fucks sake.

>>107167953
YES. THEY. DO.

t. seething half the time looking for HQ PNGs to upscale via transformers watching JPG crusties get blow up as well.

People = shit. Have you learned nothing listening to slipknot?

>>107167921
>he's gonna buy an nvidia gpu to save a few minutes converting family photos
weird flex but ok. maybe there's a usecase for avif somewhere out there but i'll still root for jxl.

>>107166747
This website is garbage dogshit trash

>>107167972
>looking for HQ PNGs to upscale via transformers

Right, so then everything you say can be safely ignored because you are part of the problem.

>watching JPG crusties get blow up as well.
could also be just webp files that people saved as png instead. because that -is- something that people do, because nobody wants to deal with that fucking cancer of a format.

>>107166865
In regards to which?