“view context” broken b̶e̶c̶a̶u̶s̶e̶ (and) lemmy.world has just joined Cloudflare (unrelated)

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?

You're viewing a single thread.

18 comments

The problem with "view context" comes from the recent update and affects all instances using version 0.18.3.
- Ah, thanks for the info. But note that there are two “show context” buttons. In principle, if I am on a broken version I should be able to visit the parent on the originating node & possibly side-step the bug. But in this case the other node blocks me (Cloudflare).
  Also note that I would still like a way to block CF instances. I’m in the #threadiverse to participate in the free world & prefer not to feed centralized walled gardens from which I am a refugee. Oppressors should not be able to thrive in the #fedi.
  #LemmyWorld is centralized in 2 ways:
  Cloudflare
  disproportionate user population
  
  But note that there are two “show context” buttons. In principle, if I am on a broken version I should be able to visit the parent on the originating node & possibly side-step the bug.
  I am not sure if I can follow you but this bug affects both "show context" and "show parent" button on broken instances.
  Also note that I would still like a way to block CF instances
  I am afraid that such a measure would only be possible for admins by blocking traffic for domains that resolve to/IP ranges operated by Cloudflare.
  
  I am not sure if I can follow you but this bug affects both “show context” and “show parent” button on broken instances.
  There is a chain link icon and a fedi icon, both of which have “show context” as mouseover text. The difference is that the chain link shows the local copy, and the fedi icon links to the source node (in the case of your msg, feddit.de). Being able to view it on the originating node also means using the web client of that other node.
  
  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 ^^
  
  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).
  
  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.

18 comments