• Gakomi@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        4 天前

        No I don’t think it does but it works. Specifically I download webp pictures on pc and when I try to send them on WhatsApp it does not recognise them so I change the extension to JPG or PNG and it works it sends them and they can be viewed.

        • tweeks@feddit.nl
          link
          fedilink
          arrow-up
          0
          ·
          4 天前

          Sounds like the file type verification on WhatsApp is not on mime-type but only on extension. Some receivers might have trouble opening these though.

          • FuzzChef@feddit.de
            link
            fedilink
            arrow-up
            0
            ·
            4 天前

            In my experience, WhatsApp does not send an image unchanged. So it doesn’t matter if the recipient can handle it, as long as WhatsApp’s conversion can

          • barsoap@lemm.ee
            link
            fedilink
            arrow-up
            0
            ·
            4 天前

            They might use standard imagemagick or such on the backend meaning they can ingest pretty much any image format ever invented, and have a limited set of extensions allowed on the frontend side so people don’t upload .txts.

          • Gakomi@lemmy.world
            link
            fedilink
            arrow-up
            0
            ·
            4 天前

            Well so far I did not encounter any issues so as long as it works I’ll still do it like this

  • dezmd@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    4 天前

    Is it still a meme when you feel it in your soul?

    I don’t know why, maybe because it’s Sunday morning and I’m just drinking my coffee and browsing around while the rest of the house sleeps in, but this triggered a rabbit hole for me. I already have a lil plugin just for quickly saving direct to PNG or JPG when I right click a WebP in my browsers, but I SHOULDN’T GODDAMN HAVE TO.

    WEBP as a wrapper (as coupled along with AVIF/AV1/VP8/etc) seems all about reassertion of corporate control of web file formats by pivoting codecs back toward patent encumbrance as a control factor, just without universal royalty hooks attached to anyone that touches even free and open software utilizing it. We were actually FREE of that bullshit for a short time. PNG has no patent encumbrance. GIF, MP3, MPEG-1, MPEG-2, MPEG-4 Part 2 all have expired patents and can be used freely.

    [Don’t get me wrong, MPEG as an org was and is pure corruption and greed, and MPEG-4 Part 2 adoption was fully diminished outside of ‘free’ circles based on their stated intention to apply a ‘content fee’ to the royalty requirements. It’s obvious why VP8 -> AV1 had to happen one way or another to break their royalty cabal insanity, but it still doesn’t taste good at all. https://en.wikipedia.org/wiki/MPEG-4_Part_2 ]

    The consortium of companies behind WebP and AV1 are all taking part in the enshittification of the entire technology sector, from web sites and web apps, operating systems, and application ecosystems. Why would we ever trust them to not rug pull the ‘irrevocable but revocable’ patent license scheme? They only put it together in the first place to end run having to pay someone who was ‘not them’ any royalties for image/video/audio encoding.


    References:

    WEBP is patent encumbered.

    https://en.wikipedia.org/wiki/WebP

    https://github.com/ImageMagick/webp/blob/main/PATENTS

    Google hereby grants to you a perpetual, worldwide, non-exclusive, no-charge, royalty-free,** irrevocable (except as stated in this section) patent license** to make, have made, use, offer to sell, sell, import, transfer, and otherwise run, modify and propagate the contents of these implementations of WebM, where such license applies only to those patent claims, both currently owned by Google and acquired in the future, licensable by Google that are necessarily infringed by these implementations of WebM. This grant does not include claims that would be infringed only as a consequence of further modification of these implementations.

    GIF is not patent encumbered since 2004.

    https://en.wikipedia.org/wiki/GIF

    In 2004, all patents relating to the proprietary compression used for GIF expired.

    PNG was never patent encumbered.

    https://en.wikipedia.org/wiki/PNG

    PNG was developed as an improved, non-patented replacement for Graphics Interchange Format (GIF)—unofficially, the initials PNG stood for the recursive acronym “PNG’s not GIF”.

    AV1, VP8, VP9, and other modernized “open source” or “free” Video Codecs all appear to be patent encumbered.

    https://news.ycombinator.com/item?id=23747923

    https://en.wikipedia.org/wiki/AV1

    https://en.wikipedia.org/wiki/AVIF

    https://en.wikipedia.org/wiki/VP8

    • barsoap@lemm.ee
      link
      fedilink
      arrow-up
      0
      ·
      4 天前

      This grant does not include claims that would be infringed only as a consequence of further modification of these implementations.

      IANAL but what they’re saying here seems to be “if you download our code and modify it and, with that modification, touch some other patent of ours we can still have your ass”. That is, the license they’re giving out only cover the code that they release. Which shouldn’t be too controversial, I think.

      The issue with codecs in general is that there’s plenty of trolls around and coming up with any audio or video codec is probably going to hit one of their patents.

      Personally, IDGAF: Software patents aren’t a thing over here. You only have to worry about that stuff if you’re developing silicon.

    • uis@lemm.ee
      link
      fedilink
      arrow-up
      0
      ·
      4 天前

      AV1, VP8, VP9, and other modernized “open source” or “free” Video Codecs all appear to be patent encumbered.

      The part about AV1 is complete FUD. MPEG LA(patent trolls, not to be confused with ISO MPEG) tried to claim that AV1 uses their patents, but failed.

    • UnderpantsWeevil@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      5 天前

      Even if it wasn’t, you could just convert it to .jpg if you felt strongly about it. Not as though there’s a compatibility issue.

      The complaint people are having is with resizing/manipulation after download. They want these enormous uncompressed files floating around on every website, in the off chance they plan to download it and manipulate it. 99.9% of the web needs to be full of megabyte sized image files for the 0.1% y’all want to play with.

    • Rob T Firefly@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      5 天前

      But the best image format to download is the original one it was uploaded in, without the recompression of server-side conversion to a lossy webp which we’re seeing all over the place.

  • brucethemoose@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    5 天前

    Webp works fine for me now.

    The problem is AVIF. I mean I love AVIF (almost as much as JPEG-XL), but it doesn’t work with anything except browser web pages, even after all this time.

    • Emerald@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      4 天前

      My only concern with jpeg xl is… how do you know if the encoded file is losslessly compressed or not?

      with jpg and png, one is lossless, one is not. But if all the files have a jxl extension, you can’t know unless the encoder adds metadata for it, right?

      • brucethemoose@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        4 天前

        I mean the application could tell by looking at how its encoded, right?

        Though I acknowledge how problematic “trusting” the app to do that is.

      • Persi@lemm.ee
        link
        fedilink
        arrow-up
        0
        ·
        4 天前

        I felt the same way about webp when it came out.

        In practice it doesn’t really matter:

        • if you’re encoding the file you know how you’re doing it.
        • if you’re receiving the file, you get the pixels you get no matter how it was encoded.
        • if you’re sending the image through some third party service, they’re going to reencode and mangle it anyway so there’s no point in worrying.

        Also, it turned out that even if it’s quite good, lossless webp is rarely seen in the wild because svg is more convenient.

    • Dozzi92@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      5 天前

      For me webp is always some gif I’m trying to text people, and now I have to go convert it.

    • thirteene@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      5 天前

      Skill issue, the only actual drawback is that some legacy systems whitelisted image extensions and haven’t been updated. Even then just take a screenshot and upload that.

      • force@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        5 天前

        I have plenty of WEBP and every image editing/viewing application I have installed can use it fine. Including, but not limited to:

        pdn, GIMP, Aseprite, Krita, InkScape, OpenToonz, IrfanView

        I think Apple users have issues with Webm & Webp? But the issue here is using Apple products in the first place. Losing 90% of basic functionality is what you expect when using one of those.

      • derpgon@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        5 天前

        All the memes I send to my friends on messenger basically come from Lemmy. I always have to download the image and use the phone image editor to crop it by one pixel. It then let’s me save it, and it saves as jpg/png by default.

  • 🇰 🔵 🇱 🇦 🇳 🇦 🇰 ℹ️@yiffit.net
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    5 天前

    I don’t understand what people’s problem with this format is except in the case of animated .gifs. I can view it. I can reupload it. It’s still an image and it still works. The exception is animations. Animations always end up as a still image when saved in that format.