[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
▼ Settings Mobile Home
/g/ - Technology

Name
Options
Comment
Verification
4chan Pass users can bypass this verification. [Learn More] [Login]
File
  • Please read the Rules and FAQ before posting.
  • You may highlight syntax and preserve whitespace by using [code] tags.

08/21/20New boards added: /vrpg/, /vmg/, /vst/ and /vm/
05/04/17New trial board added: /bant/ - International/Random
10/04/16New board for 4chan Pass users: /vip/ - Very Important Posts
[Hide] [Show All]


[Advertise on 4chan]


File: 1767656467083173.png (13 KB, 1024x1024)
13 KB PNG
>>
Where?
>>
OH GOD, they're using a better image format that saves them literal money on hosting costs long term but doesn't rape your CPU to death.

Somebody needs to leak this to the press, we can't keep daiz getting away with this! This is pretty much another SHOA!
>>
haha now rapeape has no choice but to use it every time he whores for attention there
>>
File: 1794870521673414.jpg (885 KB, 352x2062)
885 KB JPG
>>110395257
>Wednesday, November 4, 2026
>Post photos, video posters, and card images are now requested as WebP.
>Our image CDN already served those URLs as WebP at roughly half the size of JPEG.

https://blog.x.com/en/engineering/rebuilding-the-global-town-square-from-scratch

>>110395390
Hmmmmmmmmmmmmmmmmmmmmmmm

That seems stupidly plausible
>>
>>110395377
Lol look at that shitty compression
PNG all the way bitch
>>
>>110395418
funny that you mention png because webp lossless rapes png to death
>>
The only reason people on this website hate webp is because 4chan is too retarded to add support.

That, and somehow it’s okay for websites to serve webp files mislabeled as other image formats.
>>
>>110395431
>The only reason people on this website hate webp is because 4chan is too retarded to add support.
nah they're just on win7 or xorg
>>
>>110395431
Why can't they just convert user webp uploads to png if full blown webp support would rape the rapeape?
>>
inter-frame logic repurposed as static image compression is inherently stupid
JXL supremacy
>>
>>110395428
Talk to aritsts instead of techie guy
>>
>>110395377
> better image format that saves them literal money on hosting costs
why do gaynigger webshitters cry about hosting costs but then require 200MB of javascript to display 3 KB of html content?
>>
>>110395447
>Why can't they just convert user webp uploads to png if full blown webp support would rape the rapeape?
Converting images would put too much strain for a site like this, can be easily exploited by the zoyjakers to DDoS
>>
File: 171375166352.jpg (206 KB, 1080x1225)
206 KB JPG
>>110395475
Because those 200MB of javascript don't come from the website directly but third parties.

The images howeverthoughbeit, actually do come from twitter.

700KB x 1 million user downloads = 5,600 Gbps

1MB x 1 million user downloads = 8,000 Gbps

Assuming you want the same image to load in 1 second. That's a lot of money for twitter. This is ON AVERAGE in case one of you daiz autists starts testing DSLR tree bark btw. There are many scenarios at which WebP will not provide any meaningful filesize reduction compared to JPG but websites don't cater to edge cases, they just want to see hosting bills go down in general.

>Compared to the reference JPEG; WebP’s median file size reduction was 31,5%
>the 85th percentile was 20%, and 2,7% of the images were larger.

https://www.ctrl.blog/entry/webp-avif-comparison/
>>
4chan's jannies still too lazy to type "claude add .webp support to yotsuba".

It's that easy, and they're that lazy.
>>
>>110395482
just do the conversion on the client's browser through js
no additional resource usage or risk

anyone smarter than a 4chan janny can figure this out
>>
File: 1661115089692.webm (2.55 MB, 640x360)
2.55 MB
2.55 MB WEBM
Can confirm webp on brave

https://pbs.twimg.com/media/HXgp83gWAAEQNO3?format=webp&name=small

I don't know what quality setting they're using though. That's been the real problem of WebP on the web for a while, they take images and rape them with quality 10 WebP encodes. I wonder if twitter will be any different.
>>
>>110395245
.png GODS stay winning
>>
>>110395659
ok but you can still access the jpg or png versions it seems
>>
File: 1422729019895.jpg (636 KB, 1000x2250)
636 KB JPG
>>110395690
For now but a lot of websites stopped serving bloated JPG after a while and the "donotserve webp" trick eventually stopped working.

https://pbs.twimg.com/media/HXgp83gWAAEQNO3?format=jpg&name=small

WebP = 16 KB

JPG = 27 KB
>>
>>110395245
it's difficult to describe exactly but webp always has this almost thin, artificial look about it. that's why everyone hates it. i'm really not sure what it is but i noticed it years ago.
>>
>>110395965
It depends on what the image source is and encoding parameters. Most people don't know this but cwebp, the thing used to make WebP images has a ton of different settings you can adjust.
-alpha_q <int> ......... transparency-compression quality (0..100),
default=100
-preset <string> ....... preset setting, one of:
default, photo, picture,
drawing, icon, text

-segments <int> ........ number of segments to use (1..4), default=4

-sns <int> ............. spatial noise shaping (0:off, 100:max), default=50

-f <int> ............... filter strength (0=off..100), default=60

-sharpness <int> ....... filter sharpness (0:most .. 7:least sharp), default=0

-sharp_yuv ............. use sharper (and slower) RGB->YUV conversion

-partition_limit <int> . limit quality to fit the 512k limit on
the first partition (0=no degradation ... 100=full)

-pass <int> ............ analysis pass number (1..10)

-qrange <min> <max> .... specifies the permissible quality range
(default: 0 100)

-near_lossless <int> ... use near-lossless image preprocessing
(0..100=off), default=100

-hint <string> ......... specify image characteristics hint,
one of: photo, picture or graph
-pre <int> ............. pre-processing filter


These are just some of the settings btw. If you actually want "Compared to the reference JPEG; WebP’s median file size reduction was 31,5%" then you have to mess with these.

That's why JPG is so popular even in 2026. You set the quality slider to 0 and everything looks like shit, set it to 50 and it's okay-ish on phones, set it to 80 and it's okay-ish on computer screens.

No having to deal with all of this.
>>
>>110395245
>Based
Based based based based!

4chin next plz. We got Mp4 support thanks to twitter fags. We will get webp in the next maintenance updoot for sure now. Thanks elon!
>>
>>110395245
So it's coming to 4xitterdiscussion next week
>>
>>110395415
>using the monkey avatar instead of his actual face
Coward meme
>>
>>110396485
The point is to make a meme, can't have a meme if it keeps getting deleted you dumbfuck.
>>
>>110396485
Also to be fair there's not much difference.
>>
Why is webp winning when jpeg xl is technically superior in pretty much every fucking way imaginable? Are twitter developers complete and utter retards?
>>
>>110395377
>implying anybody uses that shit tier quality jpg
Compare high quality JPG to the same size in webp, faggot.
>>
>>110396628
>Are twitter developers complete and utter retards?
...yes?
>>
>>110396628
Compatibility.
Chrome and Firefox dragged their feet supporting JXL and now their are still loads of browsers based on older versions of the engine in the wild without any support.

Notice how Edge, despite being based on modern Chromium still doesn't even have support. Now you might think "Who the fuck uses Edge" and you'd have a point but they still have to support it.

Microsoft really needs to get their act together.
>>
If google weren't retarded monkeys who failed to offer proper support for the format they themselves were trying to force, it would probably be standard now and nobody would have a problem with it.
>>
>>110396636
>"brrrrroooooo broooo, if you jack up the file sizes to where they cost websites trillions of dollars per second, JPG wins!!!!"
kek
>>
>>110396665
anything other than chrome or firefox is irrelevant
>>
>>110396698
It's all Chrome or Firefox (apart from Safari which is Webkit based).

You can't not support Microsoft Edge though as it's the default browser on Microsoft Windows even if everyone just uses it to download Firefox or Chrome you're doomed to forever need to support it.

It's really fucking stupid that they deliberately disable JXL support for no reason. They are the last holdout.
>>
>>110396665
I'm an edgelord
>>
>>110395965
>>110396023
cwebp desaturates the source image if you forget to include the -sharp_yuv flag when converting to WebP. The retarded jeets at google turned it off by default.
>>
>>110395377
Keeping it exactly the same as the original quality is what matters. Let people who don't care or don't know better get the reduced quality version.
>>
File: tzw6ud001e261.jpg (276 KB, 1080x1661)
276 KB JPG
>>110396975
So who's going to pay for the added network strain using -quality 100 images is going to use. YOU, the same cocksucking motherfuckers using ad-blocking?
>>
>>110397035
...You?
>>
>>110397035
If they didn't want large images, they could put a tiny cap on image size and resolution to upload. Make then max out at 200x200 or something, and don't allow more per post than they used to.
>>
>>110396739
whoa, thanks anon. this is the first time i've seen any explanation.
>>
>>110395245
>I HATE new!! New trigger muh neuroretardation ticks!!! AIEEEEEEE
>>
>>110397580
who are you quoting?
>>
>>110397596
OPs implication.
Also, it's "whom".
>>
>>110395245
Good. Stay there.
>>
Just because WebP is worse than JXL or AVIF doesn't mean you shouldn't support it. Web browsers already fucking support it. It's an open standard. The images you find on the internet are WebP. I should be able to post WebP on 4chan.

>>110395671
So already transcoded image but you decide to store it as more bytes. That's retarded.
>>
File: 1761767612536712.webm (41 KB, 1056x720)
41 KB
41 KB WEBM
>>110397627
It's because google made webp and these fucking lemmings would shit on jxl if google made it as well.
>>
>>110395671
except you can't save transparent JPG
>>
>>110398442
>transparent JPG
????
>>
>>110398472
he's trippin
>>
I'm guessing the old :orig workaround doesn't work anymore, right?
>>
>>110395245
fags mad because rapeape still won't let them upload their twatter webp's
>>
>>110395428
webjeets wants to have sex with pngs because theyre fags. shows bobs please mona lisa.png
>>
>>110395428
this isnt lossless encoding though, its "virtually" lossless which is just another form of lossy encoding, just not really noticeable
>>
>>110395377
webp loses all its appeal when you realize nobody is saving their images as webp EVER. So essentially what webp actually means is that we get lossy to lossy conversions, and this is all over the entire fucking internet.

Every fucking jpeg is already lossy, they already look bad at a lot of the time, and now we have another layer of lossy ontop of that. It doesn't matter that webp is better at compression, because it is compressing from lossy.
>>
>>110395965
its because webp is misusing a video codec for still images
videos can look hazy because most of it just appears as (pre existing) motion blur, but for still images its ridiculous
>>
>>110395438
I'm on XP and don't even care. Makes no real difference one way or the other.
>>
>right click
>take screenshot
not my problem
>>
>>110395245
The end is here.
>>
>>110395257
>>110395245
Should serve jxl instead
>>
>>110395245
Can someone explain to me what's the big deal with people whining about webps? My system sees the webps as literally the same as other images, and if in some rare old application or something needs png or jpg I can just magick convert it on the drop of a hat. Is this a Windows thing where its photo viewer and thumbnails don't support it?
>>
>>110400746
try posting a webp here
>>
>>110400908
ez pz
>>
File: 1.png (301 KB, 550x368)
301 KB PNG
>>110400908
>>110400953
It was just a drag and drop. You do have the 4chan extension that automatically converts webp to png, right anon?
>>
>>110400959
NO I DONT I DIDNT EVEN KNOW IT EXISTED ACTUALLY
>>
>>110400966
tech illiterate kun...
>>
>>110400966
It's something called 4chan X. However it's been a while since I've installed it, it must have changed five names and maintainers since then.
>>
>>110400981
there must be more than one then because mine doesnt do that
>>
>>110400959
Infinite recompression!
>>
>>110400601
retard

>>110400602
fair point but GIMP/Photoshop now support WebP export so that should improve soon.

>>110400734
look at how CPU intensive it is in >>110395377

JXL is a cool concept and all but it's still, practically speaking, in the BETA stage. When decoding does get better it would be better to go from WebP to Jpeg XL instead of AVIF. I think we can all agree on that.
>>
File: 1776832681299626.png (62 KB, 240x240)
62 KB PNG
illiterate and uninformed-kun over here. why is this a bad thing. arent more efficient open formats better. or is this about artists/professional workflows being interrupted
>>
>>110403099
no it's about 4chan jannies being too retarded to implement it here
>>
>>110403099
>or is this about artists
it's about autists who use deprecated shit
>>
File: 1766634194419823.png (137 KB, 643x698)
137 KB PNG
>>110403121
well i mean we could blame the art software companies instead. artists just be arting with workflows that be working. we love artists. they make some good fucking foodf
>>
File: duck-laugh.gif (301 KB, 220x123)
301 KB GIF
>>110395245
That fag ape will be forced to use a format he refuse to implement (aside updating his dogshit backend).
>>
>>110403099
There's basically 3 reasons to hate webp
>you hate (lossy) recompressed images in general because some of the quality was lost, not unique to webp of course but since nobody actually saves their own files as webp you know it's always recompressed by the website
>you're using an image viewer that doesn't support it but really don't want to use anything else
>can't post them on 4chan
>>
>>110403213
> you know its always compressed (lossy) by the website
ah, thats understandable. it does suck getting lossy compressed images

> image viewer doesn't work
for the second one, it seems that may be a windows problem? not trying to be antagonistic. im running Fedora KDE and
gwenview
for images/videos and haruna for videos just work for everything ive seen. it could just be windows default built in image/video viewers not supporting the formats?

> cant post on 4chan
Anon...
>>
File: anne-the-mennace.png (95 KB, 1168x1060)
95 KB PNG
>>110403099
see >>110395377

The criticism of WebP mostly come from autistic individuals that cannot conceptualize that people have different thoughts than themselves and that the world must revolve around them. When normal people go on the internet they don't all have flagship phones, perfect 5G coverage, or high end gaming PCs hooked up to 10Gbps fiber optic home ISPs. You have to understand that from their point of view other people do not exist as separate individuals but as extensions of themselves. So ultimately they can't conceptualize why the world might be worried about things like decoding performance. Which was something WebP struggled with until recently btw.

Besides decoding performance there is also image editor/viewer, content management system, messaging apps, and browser support to worry about. Those are all things at which WebP has recently gotten a lot of support in. It could take a decade before Jpeg XL or AVIF achieve that level of support.

>"One of the most recurrent problems throughout middle childhood was my constant failure to distinguish between my knowledge and that of others. Very often my parents would miss deadlines or appointments because I failed to tell them of these matters. For instance, my parents missed the school’s Open House in my fifth grade and my mom asked me afterward ‘why didn’t you tell us about it?’ ‘I thought you knew it’, I replied."

https://www.open.edu/openlearn/mod/oucontent/view.php?id=67018&section=1.3
>>
>>110395245
Of corse it does, Elon loves trannies and webp is tranny tech.
Next step is migrating everything to rust.
>>
File: ashby.jpg (147 KB, 617x1200)
147 KB JPG
See what I mean? >>110403316 did not even bother reading anything posted in this thread because he can't fathom that people have different thoughts than him.
>>
>>110403337
I NEED a cute autistic gf bros.
>>
>>110403286
>It could take a decade before Jpeg XL or AVIF achieve that level of support.

Webp took a decade to get meaningful support because iphones never supported it.

Iphones already support Jxl and Avif. Jxl also supports transcoding jpg without quality loss, which was the biggest problem that Webp had.

AV1 videos are already used on some video sites.
>>
>>110396665
>and now their are still loads of browsers based on older versions of the engine in the wild without any support.
And when you combine every single one of those older versions, you still don't hit 2% of global usage. Except maybe if you count Edge.
>>
>>110403819
>Webp took a decade to get meaningful support because iphones never supported it.
They didn't support it because WebP had poor decoding performance. Now that's not the case anymore so they added support.

>Iphones already support Jxl and Avif.
Only the iPhone 16 series from 2024 have CPUs powerful enough to decode high resolution Jpeg XL and AVIF images. Anything older than that struggles and will have to fallback to WebP images. Also everyone on earth does not own an iPhone, in most of the world used 10 year old Android phones are very common but most of them can handle WebP decoding just fine.

>Jxl also supports transcoding jpg without quality loss, which was the biggest problem that Webp had.
This probably won't be used. It's a nice feature but there's no guarantee that a website will use it because lossy compression achieves smaller filesizes.

>AV1 videos are already used on some video sites.
Irrelevant in the discussion of image codecs here.
>>
File: firefox_DbsNho2MFN.png (94 KB, 1171x1016)
94 KB PNG
Is there a NitterPlease alternative that lets you select the rogue nitter instances? Those fucks want me to LINK my phone to that site now! Fuck off!
>>
>>110404308
libredirect o algo
>>
>>110404318
Nope, no x
>>
>>110404376
anon it's right there in the settings
>>
File: firefox_kVtZazu4u4.png (33 KB, 310x466)
33 KB PNG
>>110404435
>>
>>110404454
click settings -> services
>>
>>110404464
You are the best, that was driving me insane.
>>
>>110395377
It's the restrictive woke globohomo file formant. You can't open it in paint, windows live photo gallery or even photoshop. It's garbage.
>>
File: 1769918762820835.png (528 KB, 962x1027)
528 KB PNG
>>110404496
So what you be saying is that POORNIGGERS get BTFO to infinity and beyond by WEBP????

HOLY MOTHERFUCKING BASED

>"With Photoshop 23.2, Photoshop provides full support to the WebP file format.
>"Open, create, edit, and save WebP files in Photoshop without a plug-in or preference setting"
>"Last updated on Aug 13, 2024"
https://helpx.adobe.com/photoshop/kb/support-webp-image-format.html
>>
Those faggot devs should just ask Claude to make their obsolete programs compatible with modern formats. No excuse to stay in the past.
>>
>>110404588
But mein fuhrer think about all the phones and computers from 2010 bursting into flames trying to decode WebP images!
>>
>>110404567
I use photoshop 7 because I’m not giving money to adobe to pay for their shitty new versions when I can get their old software for free and it does everything I need it to.
>>
>>110395245
oh no
>>
File: all are webm.png (581 KB, 1321x451)
581 KB PNG
>>110398472
pic related
>>110398495
>name callout
No
>>
>>110395377
That benchmark pic is very outdated. Webp has all of the problems of jpeg and it's limits to color depth and resolution are just retarded. Maybe 15 years ago it would have been a good format, but using 8bit colors in todays age? And it can't even be used for large images? What's the point? Focusing so much on file size in the age of fast fiber optic internet is just stupid. What we need is a future proof high quality format without stupid limits.
>>
>>110405237
Soooooo decoding performance = not important?

We all just pretend those gorrillions of fire HD 8 tablets out there are the same thing as iPhones?


Seriously?
>>
>>110405237
jpeg xl decoding has improved but it's still not as fast as webp. Why would you even expect it to achieve that? WebP was derived from a 2008 proprietary video codec that google bought and made open source so people wouldn't get raped with royalty payments for using it.
>>
>>110405237
>Webp has all of the problems of jpeg
JPG doesn't support transparency or animations.
>>
is it just me or does firefox not support pasting webp from the clipboard wtf
>>
File: image8_proc.png (151 KB, 1585x1180)
151 KB PNG
>>110405306
Firefox doesn't even support HDR yet, it's the most dogshit web browser ever after it went political and fired all its competent devs. Why do you think Brave exists?
>>
>>110405274
>>110405288
Decoding speed is important, but fast enough with jpeg xl. The difference is only noticeable for very large images and it's only a few hundred ms in those cases. You wouldn't even notice the difference on 99.9% of websites.
>>
>>110395377
You WILL accept this webp
NO, we don’t want it back
>>
>>110405325
Brave is retarded and Indian.
>>
>>110395245
Why not jpegxl? I don't get it.
>>
File: microslop.png (445 KB, 1000x1044)
445 KB PNG
>>110405325
It supports HDR on Linux and macOS. Stop using Microslop.



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.