I was trying to work out why it is that when I receive a notification and I click “view context” nothing happens if the msg came from lemmy.world. The screen blinks for a second but gives no prior posts. Well after digging into this, I see that #lemmyWorld has just recently joined the exclusive #walledGarden of Cloudflare.

I think I don’t want users of Cloudflared instances to see my posts because it invites broken interactions. Is there any way to block CF instances at the individual account level?

  • nachtigall@feddit.deEnglish
    2·
    11 months ago

    Oh I see. So you accessed a comment on lemmy.world via the fedi icon and the Cloudflare proxy blocked you. Are you using Tor or a VPN? Because that never happened to me without either ^^

    • diyrebel@lemmy.dbzer0.comOP
      11·
      11 months ago

      It’s complicated. I first used the chain link which is purely internal. This expands the msg and offers the “show context” option which gives nothing (due to the bug). Then I try the fedi icon and nothing happens at all… no expansion or anything. But I can see that the button is sensitive because it flashed as I clicked it. So then I forcefully copied that external link into a new tab in Tor Browser and it just shoots a blank. No text at all. Then I copied that same Lemmy World link into ungoogled chromium running over tor, which shows #LemmyWorld’s blockade I screencapped.

      Note that ungoogled chromium has experimental value and reveals the problem (Cloudflare), but all versions of #Lemmy I have encountered have always been wholly broken in ungoogled chromium. Lemmy forces the use of Firefox-based browsers (and last time i checked Lemmy is quite useless in text browsers as well).

      • nachtigall@feddit.deEnglish
        3·
        11 months ago

        Then I try the fedi icon and nothing happens at all… no expansion or anything. But I can see that the button is sensitive because it flashed as I clicked it. So then I forcefully copied that external link into a new tab in Tor Browser and it just shoots a blank.

        Indeed. I can reproduce this behaviour with this comment from this thread. See the following screenshot from my network console. The body says {“error”: “not_logged_in”}, so maybe a caching error or something like that? I’ll ping the admin of lemmy.world

        running over tor, which shows #LemmyWorld’s blockade I screencapped.

        That makes sense. Cloudflare often blocks Tor IPs or spams them with captchas.

        have always been wholly broken in ungoogled chromium.

        No problem on my side.