• YoSoySnekBoi@kbin.earth
    link
    fedilink
    arrow-up
    35
    arrow-down
    1
    ·
    13 hours ago

    Mainly a compatibility thing afaik. For web stuff it’s actually pretty great but people don’t like not being able to download it in a format that works with image viewers and editing apps

    • FaceDeer@fedia.io
      link
      fedilink
      arrow-up
      22
      ·
      13 hours ago

      So it’s basically “nobody wants to use it because nobody is using it.”

      I actually rather like it, and at this point many of the tools I use have caught up so I don’t mind it any more myself.

      • ɯᴉuoʇuɐ@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        3
        ·
        7 hours ago

        My impression is that for ordinary non-power users it was supported from the start (i.e. the commonplace image viewers and editors could open it - at least I personally had no issues), it just felt annoying at first because it seemed forced upon the user.

      • FaceDeer@fedia.io
        link
        fedilink
        arrow-up
        8
        ·
        7 hours ago

        It works because the .png and .jpg extensions are associated on your system with programs that, by coincidence, are also able to handle webp images and that check the binary content of the file to figure out what format they are when they’re handling them.

        If there’s a program associated with .png on a system that doesn’t know how to handle webp, or that trusts the file extension when deciding how to decode the contents of the file, it will fail on these renamed files. This isn’t a reliable way to “fix” these sorts of things.