No I don't think it does but it works. Specifically I download webp pictures on pc and when I try to send them on WhatsApp it does not recognise them so I change the extension to JPG or PNG and it works it sends them and they can be viewed.
They might use standard imagemagick or such on the backend meaning they can ingest pretty much any image format ever invented, and have a limited set of extensions allowed on the frontend side so people don't upload .txts.
I don't know why, maybe because it's Sunday morning and I'm just drinking my coffee and browsing around while the rest of the house sleeps in, but this triggered a rabbit hole for me. I already have a lil plugin just for quickly saving direct to PNG or JPG when I right click a WebP in my browsers, but I SHOULDN'T GODDAMN HAVE TO.
WEBP as a wrapper (as coupled along with AVIF/AV1/VP8/etc) seems all about reassertion of corporate control of web file formats by pivoting codecs back toward patent encumbrance as a control factor, just without universal royalty hooks attached to anyone that touches even free and open software utilizing it. We were actually FREE of that bullshit for a short time. PNG has no patent encumbrance. GIF, MP3, MPEG-1, MPEG-2, MPEG-4 Part 2 all have expired patents and can be used freely.
[Don't get me wrong, MPEG as an org was and is pure corruption and greed, and MPEG-4 Part 2 adoption was fully diminished outside of 'free' circles based on their stated intention to apply a 'content fee' to the royalty requirements. It's obvious why VP8 -> AV1 had to happen one way or another to break their royalty cabal insanity, but it still doesn't taste good at all. https://en.wikipedia.org/wiki/MPEG-4_Part_2 ]
The consortium of companies behind WebP and AV1 are all taking part in the enshittification of the entire technology sector, from web sites and web apps, operating systems, and application ecosystems. Why would we ever trust them to not rug pull the 'irrevocable but revocable' patent license scheme? They only put it together in the first place to end run having to pay someone who was 'not them' any royalties for image/video/audio encoding.
Google hereby grants to you a perpetual, worldwide, non-exclusive, no-charge,
royalty-free,** irrevocable (except as stated in this section) patent license** to
make, have made, use, offer to sell, sell, import, transfer, and otherwise
run, modify and propagate the contents of these implementations of WebM, where
such license applies only to those patent claims, both currently owned by
Google and acquired in the future, licensable by Google that are necessarily
infringed by these implementations of WebM. This grant does not include claims
that would be infringed only as a consequence of further modification of these
implementations.
PNG was developed as an improved, non-patented replacement for Graphics Interchange Format (GIF)—unofficially, the initials PNG stood for the recursive acronym "PNG's not GIF".
AV1, VP8, VP9, and other modernized "open source" or "free" Video Codecs all appear to be patent encumbered.
This grant does not include claims that would be infringed only as a consequence of further modification of these implementations.
IANAL but what they're saying here seems to be "if you download our code and modify it and, with that modification, touch some other patent of ours we can still have your ass". That is, the license they're giving out only cover the code that they release. Which shouldn't be too controversial, I think.
The issue with codecs in general is that there's plenty of trolls around and coming up with any audio or video codec is probably going to hit one of their patents, so the best that FLOSS codecs can do is "we don't have any patents on this" or "we do have patents on this but license them freely, also, if someone else goes after you we're going to detonate a patent minefield under their ass". Patent portfolios have essentially reached the level of MAD.
Personally, IDGAF: Software patents aren't a thing over here. You only have to worry about that stuff if you're developing silicon.
But the best image format to download is the original one it was uploaded in, without the recompression of server-side conversion to a lossy webp which we're seeing all over the place.
Even if it wasn't, you could just convert it to .jpg if you felt strongly about it. Not as though there's a compatibility issue.
The complaint people are having is with resizing/manipulation after download. They want these enormous uncompressed files floating around on every website, in the off chance they plan to download it and manipulate it. 99.9% of the web needs to be full of megabyte sized image files for the 0.1% y'all want to play with.
The problem is AVIF. I mean I love AVIF (almost as much as JPEG-XL), but it doesn't work with anything except browser web pages, even after all this time.
My only concern with jpeg xl is... how do you know if the encoded file is losslessly compressed or not?
with jpg and png, one is lossless, one is not. But if all the files have a jxl extension, you can't know unless the encoder adds metadata for it, right?
All the memes I send to my friends on messenger basically come from Lemmy. I always have to download the image and use the phone image editor to crop it by one pixel. It then let's me save it, and it saves as jpg/png by default.
I think Apple users have issues with Webm & Webp? But the issue here is using Apple products in the first place. Losing 90% of basic functionality is what you expect when using one of those.
The 1996 free breakfast cereal promotional game Chex Quest (which is actually a total conversion of Ultimate Doom with much of the original data intact).
Skill issue, the only actual drawback is that some legacy systems whitelisted image extensions and haven't been updated. Even then just take a screenshot and upload that.
I don't understand what people's problem with this format is except in the case of animated .gifs. I can view it. I can reupload it. It's still an image and it still works. The exception is animations. Animations always end up as a still image when saved in that format.
Pretty much everything supports it now, and in case you haven't noticed pretty much all the images on Lemmy are webp because it lets instances save tons and tons on bandwidth and storage.
The next "better but not yet supported" image format is .avif.
Now we just need a Brennan Lee Mulligan flavored fully charged rant about the billionaire class of corporatists forcing webp with its patent encumbrance on us all.
I actually decided to use avif on my project. But both this and webp is as fast as I know, not supported in any default image viewer on windows. Which is rater annoying, but I moved on to better programs for tgat anyways.
Avif is second to jxl though, some of the downsides of being a video format is that you loose progressive loading (only top to bottom iirc), degrades on re-encodes, and some other things I can't think of. Avif gets a win because if you have a av1 decoder you already have a avif decoder too! But since it is a video frame essential there are some downsides since some image specific features can't or won't be added.
Not the end of the world, but out of the few apps that don't fit in the 'pretty much everything' group, messenger is one of them and I can't share a good bunch of memes on Lemmy with my friends because of that. I usually end up screenshotting my own screen because of that.
Every time I have to fire up my Fb account, I'm stunned at how shit React is. It's appalling how bad that framework has become. Maybe if they cared about implementing solid code and less about raping your life of metadata in order to sell you the worst products on the planet thru their "partners" things would be better.
What doesn’t support avif? Even Apple devices support it and they are usually the last to adopt anything. I’ve crushed all my website using it and it turns a 1MB image to 80KB without quality loss, absolutely amazing compression!
In websites it works great, there isn't a browser around that can't deal with it. Same how with when webp was new you'd run into it all over the web because there they were just better and worked fine.
It's everything else that isn't ready yet. My older android device can't deal with them in apps, no AV1 decoder maybe? Dunno.
Not many processors have AV1 hardware decoders yet (Apple thru them in on their M3's last year and latest iPhone 15 Pros) so I can't see it being that. There's also software decoding that works fine. My wallpaper on macOS has been avif since last year (Sonoma) and works without issue. I don't think it works in Windows 10 tho. No issues with the latest Ubuntu and I'm not familiar at all with Android OS.
In any case, I think it's the best thing to come out in a long time. My website with raw PNGs was about 120MB. I crushed those PNGs with noticeable quality loss down to 50MB. I then crushed the original 120MB down to 60MB with minimal to no visual quality loss using webp. But I got it down to 25MB without loss using avif at 85% compression. Just insane performance, couldn't be more impressed!
Okay can someone please explain why Facebook Messenger on my phone keeps saying it can't support gifs? Yes yes I'm an old man, but on the other hand what the fuck, fucking gifs? Are they devolving faster than Google?
(Also like, the gif feature built into Facebook Messenger itself. The longer I think about this problem, the more I think the app is just throwing the wrong error)