Fucking autocorrect had it as ‘rage’

  • poVoq
    link
    fedilink
    45 months ago

    Hmm, you are the first person complaining about this and I can’t seem to replicate it either.

    What browser and operating system (incl. version) are you using?

    • @Agrivar
      link
      25 months ago

      Firefox 127.0.2 with uBlock Origin (and many other extensions) on Windows 10 Pro, Version 21H2

      • poVoq
        link
        fedilink
        25 months ago

        Hmm, those should be all fine, but maybe another extension is the issue? Since you likely have it installed anyways, can you check if the images load in a clean Edge or Chromium browser?

        • @Agrivar
          link
          15 months ago

          Could it be HTTPS-everywhere causing it? Not that I’ll disable that just to see some memes, but at least I’ll know what’s going on…

          • poVoq
            link
            fedilink
            25 months ago

            No, the images are clearly served over HTTPS here. I suspect it might be a disagreement over the exact version of TLS being used as I admit my configuration of that is a bit amateurish, but you must have configured some rather extreme hardening measures for that to have such a result.

            • @Agrivar
              link
              15 months ago

              I haven’t manually changed anything, to be honest. My entire security setup is based on copying what I read on sites like this - I’m thirty years out of IT and can’t be arsed to stay up to date.

              • poVoq
                link
                fedilink
                25 months ago

                Then I am at a total loss. You seem to be the only one affected, or at least the only one that told us so far and it is a reasonably popular server.

                We do use the new image proxy feature on Lemmy, which still has some bugs to iron out, but that has also been running a few weeks now, without anyone having major issue like you seem to have.

        • @Agrivar
          link
          1
          edit-2
          5 months ago

          Edge 126.0.2592.102 with no extensions:

          Hmmm… can’t reach this page It looks like slrpnk.net closed the connection Try:

          Checking the connection Checking the proxy and the firewall ERR_CONNECTION_CLOSED

          essentially the same error in Chrome.

          • poVoq
            link
            fedilink
            2
            edit-2
            5 months ago

            So the entire page fails to load? Very odd. You run something like Pihole to filter the entire network traffic?

            • @Agrivar
              link
              15 months ago

              Nothing at all is filtering the home network, I’m ashamed to admit. It’s just a Comcast modem with 4 computers plugged into its ethernet lines.

      • @mrvictory1
        link
        05 months ago

        FF nightly 129 with ublock origin, Android. No issues on my end. Does it appear if you use vpn?

        • @Agrivar
          link
          15 months ago

          I am using a vpn now, and have been for about a week, but this problem has been going on longer than that.