It seems like either
-
I get a
.webpfile when I don’t want it (downloading images) -
I try to use a
.webpformat, but it isn’t allowed (uploading images)
So who is trying to encourage people to use it, and who is trying to prevent adoption?
I’m constantly converting it with imagemagick and other tools
I like webp for space and bandwidth reasons (300 KB PNG -> 35 KB webp) but support among applications/services seems spotty.
Like, my phone’s gallery supports webp no problem. But Google Voice or my phone’s SMS app will not handle them at all. I don’t have a converter app, so I open it in gallery, take and then crop a screen shot if I need to send it to someone (crude but effective).
With Lemmy, a lot of admins force conversion of uploads to webp on the backend to save storage costs and reduce bandwidth. If you want to get a different format, such as png, you can add
?format=pngto the end of the image URL. That’s one of the options I’m working to add to my custom UI (download image as [webp, png, jpg] ) because I’ve run into the same problems as you when trying to share things from here.lossless png vs butchered webp is not a fair comparison.
It’s not, but for memes and shit, IDGAF about lossy vs lossless. I just don’t want to have to jump through hoops to text it to a friend.
And for image storage on my instance, I’m not paying for people to upload lossless images. They can take webp or not upload anything :P
I think they meant comparing with jpeg might have been a fairer comparison.