fucking Telegram automatically converts any webp sent in a message to a fucking sticker
I didn't want that. I want the ability to view the image, including zooming in and panning, and telegram forcing it into a sticker kills that completely
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to [email protected]
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.
A collection of some classic Lemmy memes for your enjoyment
fucking Telegram automatically converts any webp sent in a message to a fucking sticker
I didn't want that. I want the ability to view the image, including zooming in and panning, and telegram forcing it into a sticker kills that completely
Whatsapp is marginally better but outside of regular sms texting I fine Facebook messenger to be the best.
Now don't get it twisted, it's still shit just the best of the shitty messaging apps.
I wouldn't know, I don't use any facebook shit
I came to bitch about the same thing.
This looks like the most relevant bug on Telegram's bug tracker for the issue: https://bugs.telegram.org/c/4360
Thanks, I thumbs upped it.
webp is absofuckinglutely inferior to JPEG-XL and that one is where you actually have that problem. I’m literally providing an avif-fallback on my website, because otherwise pretty much no browser would support anything.
(Speaking of it, avif is also superior to webp.)
I'll take ASCII art over webp.
The true best form of image storage. Nothing beats .txt
miss the days when I could watch the entire matrix movie on ascii before BitTorrent and streaming
Some dude ran a public telnet server, which upon connecting, would present to you the entirety of Star Wars: A New Hope in ASCII. It was glorious.
for my use cases of memes or a PowerPoint type thing once in a while for school. Literally any image format works for me. I don't care about quality (as long as it's not REALLY bad) and just want to get the image from Google to the PowerPoint, and somehow GOOGLES own image format fails to work for GOOGLES PowerPoint product.
I don't understand how you can not support your own format 10 years after it came out.
pro tip by the way, you can open it in Microsoft paint then "save as -> .PNG" to get Google slides/whatever to accept it.
(before someone recommends alternatives, im talking about use on a locked down school computer. I can't use alternative software that's better because they block images in WIKIPEDIA, no shot for using an actual foss software lmao)
use on a locked down school computer.
Shift + Win + S
I'll bet they didn't disable that in Group Policy. Lasso that sumbitch right off your screen and then just paste it into whatever.
Paint trick would leave the option for higher quality, a screen grab leaves you at screen grab resolution.
I recently put in a lot of hours for a software system to be able to handle webp just as well as every other image format it already accepted. I put in a lot of work as well. Hadn't heard about it for a while, but saw the feature release statement for the new version I knew my changes were in. It wasn't on there. So I reached out to my contact and asked if there was an issue or did it get bumped to a later version or what? So she told me the marketing team that do the release statements decided not to include it. They stated for one, people already expect common formats to be handled. Saying you now handle a format looks bad, since people know you didn't handle it before and were behind the curve. The second (probably more important) reason was nobody knew what webp even was and it's only something technical people care about (they probably said nerds, but my contact translated). So no regular customer would be interested and it could only lead to confusion and questions.
I hope somebody is happy with the work I put in tho. Somebody is going to drag a webp into the system and have it be accepted. Someday.... I hope...
Maybe I worded it incorrectly. The feature was released in that version. They just didn't mention it in the release statement they put out to their customers. I'm sure there's some changelog somewhere people can dig into where it says something like what you mentioned. Or it can just be under "Various small improvements" which they always add as a catch-all.
So I'm happy, I did the job and got paid. Everyone I worked with was happy. And the feature got released. It's was just a let down it didn't get mentioned at all, even though I put quite a lot of work into it.
I will second the suggestion at something like "expanded support for more image formats". One of my responsibilities is rolling the development log into customer release notes and I agree with the "changes that highlight a previous shortcoming can look bad", and make accommodations for that all the time. I also try to make sure every developer that contributed can recognize their work in the release notes.
"Expanded image format support" seems like something that if a customer hasn't noticed, they would assume "oh they must have some customer with a weird proprietary format that they added but have to be vague about". If it were related to customer requests, I would email the specific customers highlighting their need for webp is addressed after pushing the release notes
The only ones reading the changelog are nerds anyway
Wait am I the only one who actually likes WEBP and is cheering for JPEG to finally die ? 😭
Webp can die. JpegXL is better in every metric and can losslessly compress existing jpeg images. The chromium team has been notably trying to kill JXL because they spent so much time on AVIF and Webp despite neither offer anything close to JXL.
No, I've heard there is dozens of you, dozens!
in my honest opinion, it’s a real shame that webp isn’t widely supported. it’s actually really great: it has awesome lossless compression, it’s so much smaller than a png while not losing any quality, it supports animation and loops, etc. it’s like jpg, png, and gif rolled into one format.
The giant jpeg square artefact on the side of Homer's head in the first frame undermines the message somewhat.
I'm not sure that's a JPEG artifact. It looks more like a video compression artifact (since the image is probably taken from a video).
I'm working on a project which generates images in multiples sizes, and also converts to WEBP and AVIF.
The difference in file size is significant. It might not matter to you, but it matters to a lot of people.
Here's an example (the filename is the width):
Also, using the <picture></picture>
element, if the users' browsers don't support (or block) AVIF/WEBP, the original format is used. No harm in using them.
(I know this is a meme post, but some people are taking it seriously)
As someone who sometimes needs a quick and dirty stock image for my work, webp is the bane of my existence. The work computers won't let me visit sites or install programs/extensions to convert the image, and my document processing programs have no fucking clue what to do with the format. There is an option in Microsoft edge to edit image, and it will dump the result as a .png which is the only workaround I've found.
Samir ?
I had a colleague code a FFT algorithm in Excel because that was the only deployment tool the customer would be allowed to use...
Since we're here and someone may find it useful, I use this: https://addons.mozilla.org/en-US/firefox/addon/dont-accept-webp/
.jxl is the better image format anyway
.jxl is still early. Webp is out for 14 years now and if support is missing its completely on the ineptitude of the client and nothing else.
I feel like jxl is supported even less than webp though
webp is completely supported by browsers I think now.
Websites still get weird about it.
JXL is supported by Safari and ummmmm mobile Safari.
The funniest thing is that even some of Google's own products don't accept Webp, like Google Voice.