@p Yeah, same here! Even in Firefox I have them disabled with image.webp.enabled=false, same for VP9 with media.mediasource.vp9.enabled and probably some other Google shit that I don't even remember of. And there've been only a few cases when I cared enough to actually download the file, convert it manually and see what's in it. Most of the time I just ignore them :marseysmug2: Problem is, I've been encountering these more and more often in the wild as of recent. I suspect, that one of the authors of some Fedi software like Firefish has decided that saving a few kilos is worth it and implemented an automatic conversion to WebP — I just can't imagine that a lot of people have decided to adopt it all of a sudden, especially with all those vulnerabilities discovered. I remember when they did it in Nitter and I had to patch this shit out myself for my instance. Why people decide to adopt it is beyond me — like I said earlier, the advantage is negligible in absolute most cases, even if it's only a few lines of code, the added complexity is not worth it. And I don't even see a lot of interest from developers TBH, there a just a few people, who run around submitting these patches and devs usually just go with it because: "Why not? Looks good on paper!" Anyway, I should probably start a media proxy or something, that would do the conversion for me. Or maybe I should just keep ignoring WebP images — haven't decided yet :marseylaughwith: @kirby@sysrq@lispi314
@lispi314 I think C has little to do with it, the biggest problem is that while it's being considered "an open standard" by many, it's not that — there is only one major implementation and it's Google's own implementation, others have little to no interest contributing to it as it will remain Google's implementation in any case. So having sole implementation that is used, in addition to obviously very popular Chrome itself, it's used by a lot of software. If that software has anything even remotely to do with images — why don't we add WebP support, right? So in addition to all the browsers, this shit is now everywhere. Why the fuck down ffmpeg in my system depends of libwebp? I don't know. Does anyone of you use WebP for any other purposes except for posting it on the Web? I don't and I doubt that anyone does — it's advantages over existing formats is negligible for personal use, but it still makes sense for Google as they serve petabytes of data and even 10% makes a huge difference. I might have digressed, but anyway — as it is used in software that is present virtually in every system and in addition to that, it's the same implementation, it makes libwebp a very attractive target for attacks. Monoculture is never good. These sole implementtion is closely studied by those, who intend to exploit it — this is where C factor might come into play. Another problem is that Google doesn't give a fuck about how and where their library is used. Because they only care about how it's being used in Chrome — Chrome offers some means of isolation, if one tab gets compromised, others are safe. And to me it looks like that is exactly what they think: "Oh, it's not that bad, it's isolated!" And that is true, and same is true for Android. But is it isolated in ImageMagic — no, it's not. And when this vulnerability has hit the news, that is exactly what one person came up with in comments on HackerNews: let's isolate/containerize it for ffmpeg and ImageMagic too. That's insane! Nowadays it's assumed that everything is isolated/containerized — but in reality it's not. And it shouldn't be! @kirby@p@sysrq
@lina Problem's with the devs merging such PRs as to them it looks like adding a new feature with zero maintenance. In reality, with all those vulnerabilities being discovered, it turns into shipping an update every time this happens. So developers and project leaders should start being more picky — and I think they will. @p@kirby@sysrq@lispi314
(schizo take) Webp is intentionally vulnerable so that they can push mandatory media signing modeled after ssl certification (c2pa.org, basically digital identity with certification authorities being the issuers). di.png
They finally gave up on GC, and with a shortage of “actually” educated developers they may have to scale back. You can’t just have a thousand people writing CoCs. :joker2:
C++ is only still popular as it ships with a compiler for a better language. Good luck trying to outrun the binary interface of C to anyone dying trying.
I finally hear people asking for templates to be removed. They’re getting closer!
> They have already added like five ways to format a string to it.
Maybe it was an interview question at Google and Guido just merged it whenever someone had a good answer.
> let's add static typechecking to Python!
Oh, they're doing this with Ruby, too. I can understand the reasoning that it makes some optimizations possible that would not be otherwise, there are new and exciting runtime errors you can experience, and there are compile-time errors, but if I wanted that, I know where to find the languages with static typing. The reason these languages are nice, the advantage they have is that you can kind of smear things around, you don't have to know where you're going, so they're great for prototyping, small scripts, exploring a weird dataset interactively.
:bwk: Kernighan gave this talk, something like "How to accidentally succeed at language design", it was really great. He talked some about awk, and noted that the domain was constrained. Then you see things like Ruby or Python or Java trying to be every language and making a mess of it; the worst offender is probably C++. I forget if it was him or dmr, but one of them said that a language that doesn't have everything is more useful than one that does.
@p They have already added like five ways to format a string to it. They way they came up with originally was horrible, but I still hate what they keep doing to this poor language, it feels like a garbage dump with all those features slapped on top of what it originally was: — Typescript is so much better than regular Javascript, let's add static typechecking to Python! — Woah, cool, les go-o!!! :marseysob: @mia@kirby@sysrq@lispi314
for f in *.webp;do echo "$f";python3 -c "from PIL import Image;Image.open('$f').save('${f%.webp}.gif','gif',save_all=True,optimize=True,background=0)";done
My point was the Next Generation will star they/thems that “focus on things more important than code” when it comes to language design like good Marxists.