• MrKaplan@lemmy.worldEnglish
      2·
      2 days ago

      Hi,

      sorry for the late response, but this is actually a problem with SJW, not with us.

      The image at https://sh.itjust.works/pictrs/image/4def1007-69c5-4d51-b227-83deef610f19.webp is not available anymore, as the underlying file has been deleted. Based on similar issues we’ve seen in the past on LW, this is likely the result of a false positive of a CSAM scanner deployed by SJW.

      @TheDude@sh.itjust.works @imaqtpie@sh.itjust.works @InEnduringGrowStrong@sh.itjust.works

      • A_A@lemmy.worldEnglish
        1·
        2 days ago

        You must be very busy, thanks for your time.

        Strange ! (i will dig and come back)

        i could swear that, at the time I wrote the comment, i verified that the link in my comment was working. Yet, the same image from lemmy.world was not linking correctly.

        i will find another, better, example illustrating what i believe was true at that time and i will then send you links that, hopefully, will stay in the same state for you to verify.

        P.S. : i can’t find anything anymore like i saw when i made that previous comment !

        • MrKaplan@lemmy.worldEnglish
          2·
          2 days ago

          It was most likely true at the time you wrote it, but it was also likely cached at the time.

          It was likely in your browser cache or Cloudflare cache when accessed from SJW, but when accessed from LW the request would be different and not hit the cache. Browsers will generally partition your cache depending on which page you’re on when fetching media to prevent certain types of attacks. For Cloudflare cache, it could have been related to certain characteristics of the request.