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
this post was submitted on 21 May 2025
1186 points (98.1% liked)
memes
14883 readers
4938 users here now
Community rules
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 !politicalmemes@lemmy.world
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
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 2 years ago
MODERATORS
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.)
Avif, the only one that I hate more than webp. 😞
Why? It’s definitely better than webp, even if google’s chrome team uses it to justify not including JXL.
I'll take ASCII art over webp.
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.
load more comments
(1 replies)
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.
True, but I'll wager most of the things people are filching for these purposes get displayed on the screen at 100% scale anyway. Unless you're sniping a picture for large format print, in which case I figure you'd probably be under less restrictive conditions... Hopefully.
You don’t even have to open it in Microsoft paint, you can just save it as a new format from the standard image viewer software.
Plus, it makes a bunch of users resort to adding extensions to their browser such as
"Save webP as PNG or JPEG 1.5.4"
which is fine but absolutely not as secure as without extensions.
load more comments
(1 replies)
skill issue
Real men use .ico
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.
it’s like jpg, png, and gif rolled into one format.
and therein lies the problem.
one tool should do one thing, and do it well.
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).
load more comments
(3 replies)
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...
a bit related.
Was working for a comparison engine. Back in the day things where slow. But i made it lightning fast. Pretty proud.
Untill a few weeks later the manager comes up, and tells me to make it SLOWER!
apparently users thought it was suss that it was so fast and the results therefore where fake…
The only ones reading the changelog are nerds anyway
- Fuck those people for telling you this after you did the work
- Those reasons are hard-stop stupid. If they REALLY cared about the marketing they'd release it silently or add a "improvements to image format handling" line and leave it at that.
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
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 there 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.
That marketing team is a bunch of absolute morons. Handling Webp would have made the comapny trendsetters.
load more comments
(2 replies)
view more: next ›