You're viewing a single thread.
It downloaded in webp. Shit.
What's wrong with WebP? It's a modern format with smaller file sizes, and most software supports it. It's very commonly used online these days instead of the legacy formats.
I download memes to share them. Messenger does not like webp. It literally won't allow me to send the image. I then have to edit the image just so I can send it. Now I have two copies of the same meme.
Which messenger? Signal and WhatsApp support it.
Edit: saw your reply below, it's Facebook Messenger. Yeah, that's a whole other problem of its own.
I thought WebP was fixed in Messenger a while back. You mean Facebook Messenger, right? I'll see if I can figure out what's up.
Yes. Facebook Messenger. I thought it had been fixed as well. It used to give an icon over the pic in the photo roll signifying it wouldn't send. Now the icon is gone and I don't find out until after failing to send it.
Just rename it into a .jpg extension instead
Seems to just work for what i need them for ¯_(ツ)_/¯
Ive had one or two that didn’t but i could open then in gimp and export that way.
Just rename it into a .jpg extension instead
Seems to just work for what i need them for ¯_(ツ)_/¯
This usually means the app supports WebP but is doing something dumb like allowing the WebP file type but not the .webp file extension. If that's the case, it's often a one-line code fix.
This happened to me in a web form, but it was with .jpg and .jpeg. I was on a phone.
On mobile?
Photoshop only recently supported webp natively. Windows barely supports webp.
Inb4 "have you heard of linux"
AFAIK Windows has supported WebP since Windows 10 1809.
In what capacity? Because the Photos app does not. Hence 'barely'. Also HEIC support is globally shit. Apple can eat a dick.
In what capacity?
The built-in APIs for handling images (GDI+) added WebP support in 1809. This is mentioned in the the documentation for the drawing library in C#/.NET, which is a wrapper around GDI+: https://learn.microsoft.com/en-us/dotnet/api/system.drawing.imaging.imageformat.webp?view=net-8.0
I haven't tried it in the Photos app recently, and don't have a Windows system handy right now to try it out, but I know it works for sure in Paint, which uses GDI+ for image encoding/decoding (and thus supports all formats that Windows itself supports).
Of course, apps that use their own encoding/decoding code might have fewer features and support fewer formats than the native Windows code.
Edit: Apparently it works fine in the Photos app if you just change the extension? Which means Microsoft is doing something weird. The code to decode WebP must be there.
The built-in APIs for handling images (GDI+) added WebP support in 1809.
The end user doesn't work with Windows API. The end user works with web sites and apps, which are rarely native these days. And there you're often limited to png/jpg for uploads.
God I love the nerd shit on lemmy
Again, barely lol
Oh god I could have just been changing the extension all along to open this stuff in Photos?? God damnit.
is "recently" less than 15 hours ago because that's when the comment was made
most software supports it
Definitely not my experience
Good luck using webp in any kind of collaborative diagramming software.
Why does that software not support modern formats though?
WebP has been around for over 10 years and practically all programming languages have image libraries that support it. Windows has had native support since Windows 10 1809, so any apps using Windows' native image encoding/decoding should support it.
Maybe because in those scenarios PNG offers sharper images, which is more important than compression when you have complex diagrams. Or because webp is more CPU intensive, and PNG gives better performance when rendering. Or because of CVE-2023-4863.
PNG offers sharper images, which is more important than compression when you have complex diagrams
WebP supports both lossy and lossless compression. Diagrams should use lossless compression so the image does not lose any quality.
PNG gives better performance when rendering
Images on the web usually aren't large enough for this to make a significant difference, and it can sometimes be offset by the quicker download time.
because of CVE-2023-4863.
libjpeg and libpng have had a number of CVEs too though.
WebP supports both lossy and lossless compression.
WebP did not always support lossless compression. It's conceivable that the tools' developers made the decision before that.
Images on the web usually aren't large enough for this to make a significant difference, and it can sometimes be offset by the quicker download time.
That does not fit the use case of diagramming tools. They usually have comparatively few assets that are used multiple times in the same document. The larger the document, the more benefit lower CPU cost has. And I've seen LARGE diagrams.
libjpeg and libpng have had a number of CVEs too though.
Fair. I'm just speculating that it might be a contributing factor for the tools still not supporting the format.
WebP did not always support lossless compression. It's conceivable that the tools' developers made the decision before that.
WebP was first released in 2010, and lossless support was added in 2011. I really doubt there were tools built between 2010 and 2011 that haven't been updated since then.
That does not fit the use case of diagramming tools. They usually have comparatively few assets that are used multiple times in the same document.
SVG is probably a better fit for this use case.
SVG is probably a better fit for this use case.
Absolutely... when available. But many companies/teams do not release SVG artwork. PNG material is much more commonly available, and actually works with these tools.
