A significant vulnerability in the WebP Codec has been unearthed, prompting major browser vendors, including Google and Mozilla (update: Mozilla has now

This affects all browsers and not just Chrome, as the media falsely reported it. Mozilla just rolled out a fix, and Brave is looking into it. This bug is likely related to the “zero-click” iOS 0day that was reported by Citizenlab last week.

  • zeus ⁧ ⁧ ∽↯∼@lemm.eeEnglish
    01·
    1 year ago

    That’s not how people use images. For an image format to be viable, you need your camera to support it, your gallery app/program to support it, the web sites you upload it to, the messaging platforms you share it through.

    yes. i agree. but that’s my exact point. if i make an image then upload it to the internet - the only software that’s involved is on my side (gimp, ps, whatever[1]) and the browser of the person viewing it. if it was supported in chromium, that’s automatically available in chrome, edge, vivaldi, brave, discord, element, spotify, whatever other chromium-embedded or electron apps you care to name. given the (unfortunate) prominence of electron-based programmes nowadays; that’s good enough for anyone who isn’t a professional, and they’re already fine. fuck it, it has the joint photographic experts group behind it - they’re quite a big name in photography

    Oh you’d be surprised… Gaming videos on Steam, screen recordings, porn clips by amateurs, or just random clips, the amount of low-res gifs with 10s of MB in size is crazy.

    meh, i haven’t seen any in the past ~5 years apart from ones specifically chosen for that 256 colour æsthetic; but i will believe you

    Sure, it’s shitty of Google to drop the support, but from experience I’m still unfortunately 100% sure it wouldn’t have gotten anywhere.

    Heck, Apple has been using HEIF for years and that’s a trillion dollar company with a huge market share, and you still get shitton of places where you can’t use it.

    it did get places. it has got places. again, it’s very new and is already well supported

    jpeg2k failed because of licencing and royalty issues[2]. heif hasn’t spread because of licencing and royalty issues. in my personal opinion, webp has licencing issues. png didn’t. jpeg (sort of) didn’t. jxl doesn’t.

    but anyways, this isn’t a pro-jxl comment; it’s an anti-webp comment. i used jxl as an example of why webp, and its adoption, is making the web worse even though it’s better than png from a technical standpoint

    1. or camera, you’re right; but i’m pretty sure that A) there are some cameras that support it already, and B) again, the jpe group have a considerable amount of sway so i’m sure they could persuade most camera manufacturers to support it ↩︎

    2. i mean, as well as the fact it didn’t really bring anything new to the table. but that’s a whole other point ↩︎