>>108205028
It's purely out of spite. RapeApe hates google.

>>108205028
They don't get paid enough

4chan has been running on absolute minimum effort for years.

I use 4chan xt so it works for me

>>108205028
All the budget and effort goes towards the April fools. Please understand.

I just wish we got AV1 support or even a larger size limit. It's hard to get any decent quality out of VP9 with a 4MiB limit.

RapeApe hates webp, it's the simple answer. He's on record saying on xitter.

This site went down for a month because some 14 year old uploaded a .pdf
We're not ready for webp

>>108205077
>Dunno frog nigger spammer, I ask myself that all the time.
I got a question. does the new jpg specs support transparent backgrounds?

>>108205251
He is right. Webp is a cancer of a format.

Idiot jannies there is no vulnerabilities on webps it was made by google a giant corporation that you know made android too snd shit effing retards

>>108205333
Nope. AFAIK jpegli devs did everything they could to remain backwards compatible with regular JPG images ao storing transparency isn't possible.

>>108205406
Only compared to jpegli, see >>108205077

If Webp is the "cancer" then libjpeg-turbo is the rabies virus.

>>108205180
They can copypaste from the vichan codebase which supports webp.
Source:4chan dot buzz supports webp :p

File: digital_data_2x.png (330 KB, 1480x564)

330 KB PNG

>>108205447
It's not the formats properties that makes it a cancer, it's the politics and the insane retarded push behind it, that forces every website to transcode high quality jpg images to turd quality webp images.

>>108205526
Funny you say that cause the image you posted is jpg snd has been reposted a bunch pf times by the looks of it so it looks like ass. Like the shitty pepes.

File: thread-1771139756585-999746292.jpg (152 KB, 1024x768)

152 KB JPG

>>108205526
It's not pretty but half the time the damage is "acceptable" as long as the original JPG was saved with high quality settings and uses 4:2:0 chroma sub sampling. Phone cameras for example due to hardware acceleration constraints save JPGs in 4:2:0 so Webp is okay here. Someone saving a screenshot of vidya and manually saving it to 4:4:4 via cjpegli is better left un-tarnished by Webp.

When I ffprobed a modern Android 16 camera image I get this:

Stream #0:0: Video: mjpeg (Baseline), yuvj420p(pc, bt470bg/unknown/unknown), 4080x3060, 25 fps, 25 tbr, 25 tbn

If anyone is curious about the technical stuff, 4:2:0 uses 50% less RAM than 4:4:4. While using 4:2:0 makes you shit and piss your pants there is a usecase for it.

File: offline.jpg (131 KB, 1600x900)

131 KB JPG

>>108205028
>Everyone
this statement is false.
Example: 4chan doesn't support webp

>>108205139
Plenty of effort here but it all goes into reporting posts to glow central

File: IMG_3082.png (2.75 MB, 960x2079)

2.75 MB PNG

Look at those artifacts. You guys attempt at defending the old crusty 90s format is pathetic.

>>108205333
JPEG doesn't but JPEG-XL does everything. Lossy/Lossless, Transparency, Animations, 10-bit / HDR, you name it.
https://jpegxl.info/resources/jpeg-xl-test-page.html
https://jpegxl.info/resources/hdr-test-page.html

File: jxl support.jpg (763 KB, 1220x2443)

763 KB JPG

>>108205670
Not even the browser support....

when i see webp i think webpiss
i can't be the only one

File: Screenshot_20260221_070840.png (588 KB, 1688x1021)

588 KB PNG

>>108205851
Skill issue.

>>108205866
Jpg xl is not a problem. It has been betamaxxed by webp which is EVERYWHERE

>>108205028
don't want pics stolen from other sites to be posted here.

File: speed.png (377 KB, 1444x1511)

377 KB PNG

>>108205851
>>108205873
Jpeg eXtra Large, while modern and obviously going to be better than a fucking 2008 image codec, requires a high amount of CPU resources which is fine for Desktop PCs made in the last 10 years. However people have this bizarre misconception that phones are just as powerful as Desktop PCs. No doubt caused by gook bench measuring how fast phones can hardware encode JPG/H264 instead of raw CPU FP64.

Anyway while a $1,000 (plus tip) iPhone may be able to decode Jpeg eXtra Large just fine, there's like a billion devices that will struggle with it. There's supposed to be a rust (lol) decoder that'll help but no one is sure if it will be enough desu senpai.

>>108205139
And thats a good thing

>>108205028
>Why doesn't 4chan support webp ? Everyone support it at this point
it's exploitable. it'd be the pdf file hacking all over again

they don't know how

>>108206430
All codecs are exploitable you just have to find an exploitable bug

>>108205028
Sorry, but changing the captcha every fucking day is a use of dev time

>>108205139
They put plenty of effort into making the user experience worse

>>108206469
It's as simple as uncommenting a line

>>108205912
The Rust decoder is SLOWER than the C++ one. They hope to improve that over time.
>So far all thats changed is that we replaced the C++ library we used for processing jpeg xl files with a rust library. Jpeg xl is still disabled via a pref by default. So does that warrant a nightly channel release note? Mostly it's a behind the scenes change so far, the new rust library hasn't been optimized as much as the C++ one yet, so it is slower to decode jpeg xl files now.
https://bugzilla.mozilla.org/show_bug.cgi?id=1986393#c49

File: 1743960607210430.png (659 KB, 1276x705)

659 KB PNG

>>108205028
>>108205139
My imageboard has support for all of the media file formats that matter (including webp and jpegxl).
Just use mine and you won't have this problem.