When I’m viewing community https://ani.social/c/ukraine@sopuli.xyz on my desktop browser, Firefox on Windows, with personal setting “Auto Expand Media” turned on, one particular post is asking me to download an .mp4 video from streamable.com: https://ani.social/post/1923262

After declining the download, the space for the expanded media is just blank.

This doesn’t happen when viewing the same /c on .ml https://lemmy.ml/c/ukraine@sopuli.xyz

On .ml, I just get a screenshot of the video.

It’s just that one post.

On other earlier and later posts of links to streamable.com videos in the same /c, I just get a screenshot.

Maybe some kind of corrupted data as that particular post was transferring over?

  • wjs018@ani.social
    link
    fedilink
    English
    arrow-up
    2
    ·
    10 months ago

    For what it is worth, it behaves the exact same way on all the instances I tried it on. sopuli, ml, world, and ani.social all will download the file when clicking the icon next to the post title. The embedded .mov file in the post body will play in browser for me in all cases.

    I am using a vanilla firefox on PopOS for reference.

    • zabadoh@ani.socialOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      10 months ago

      Did you have the “Auto Expand Media” setting turned on in your Lemmy preferences?

      I believe that’s where the download request happens when just viewing at the /c level.

      • wjs018@ani.social
        link
        fedilink
        English
        arrow-up
        1
        ·
        10 months ago

        Yep, that was it. The file downloaded at the /c/ level after checking that box for this instance and didn’t for the ml instance. I tried to check how the behavior is different on the world instance where I have an account, but saw that option isn’t there since they are still running lemmy 0.18. So, it seems like that is a recently added option, perhaps some lemmy version differences that aren’t visible just through the version number at the bottom of the page?

        Alternatively, the only other thing I could think of is some weird webserver setting differences. I only know enough about nginx configs to get myself in trouble, so I can’t even begin to try to diagnose it though.