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?

  • BURN@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I’d just like to know what your solution to DDOS and other bad actors is if it’s not cloudflare. The Lemmy Devs don’t have the bandwidth to waste time reinventing the wheel on something cloudflare already does extremely well.

    A walled garden means there’s actual barriers to entry. Cloudflare isn’t a barrier to entry unless you’re planning to attack an instance or are using something like ToR as your daily browser.

  • nachtigall@feddit.de
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    The problem with “view context” comes from the recent update and affects all instances using version 0.18.3.

    • diyrebel@lemmy.dbzer0.comOP
      link
      fedilink
      arrow-up
      0
      arrow-down
      1
      ·
      edit-2
      1 year ago

      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