4
“view context” broken b̶e̶c̶a̶u̶s̶e̶ (and) lemmy.world has just joined Cloudflare (unrelated)
(lemmy.dbzer0.com)
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?
If that's true then why are there reports of the attack bringing them down on July 15th?
That was a lemmy exploit that someone gained admin credentials through the cookies. Quite a few lemmy servers were targeted, but many were able to patch quickly once it was reported through lemmy.world.
Your timeline is backwards. The account compromise was July 10; the DoS attack came after that (July 15th). There is also no chatter of any kind about any attacks prior to July 10th.
You are correct. The issue in your post isn't caused by cloudflare though, it's caused by the update to 0.18.3.