• tal@lemmy.today
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    8 hours ago

    Honestly, I think that the right route is to update them. Especially on the Threadiverse, where the server time is donated and images are the big storage/bandwidth consumers—I’d rather do what’s possible to keep costs down. My own favorite Android client, Eternity, is unmaintained and can’t do AVIF, which I think is unfortunate, but I can view them externally using a browser and I suspect that unless someone decides to take over maintenance, I’ll probably need to switch clients anyway. Either clients get maintained or ultimately die to bitrot…

    When I’ve uploaded images recently, I generally submit AVIF and then also include a WebP link in the body or a comment for older clients. In this case, it sounds like the instance may be transcoding to AVIF, so that probably isn’t an option.

    EDIT: Well, I thought that it couldn’t do AVIF, but…somehow I can view it in Eternity. Huh. I did change Android devices recently. Not sure if that’s a factor.

    EDIT2: Ah. Sounds like Firefox has app-level AVIF support, and Android 12+ has OS-level support. Might be that Eternity had been relying on the OS.