Huh?

  • 0 Posts
  • 22 Comments
Joined 6 months ago
cake
Cake day: June 8th, 2025

help-circle



  • You don’t get hacking protection from bots, you get protection from DDoS attacks. Yeah some customers would have gone down, instead everyone went down… I said that instead of crashing the system they should have something that takes an intentional decision and informs properly about what’s happening. That decision might have been to clo

    You can keep the policy and inform everyone much better about what’s happening. Half a day is a wild amount of downtime if it were properly managed.

    Yes, bot detection is not the most critical…

    So you agree that if this were controlled instead of open crahsing everything them being able to make an informed decision and opening or closing things, with the suggestion of opening in the case of not detection is the correct approach. What’s the point of your complaint if you do agree? C’mon.


  • They probably mean that they did a change in a config file that is uploaded in their weekly or bi-weekly change window, and that that file was malformed for whichever reason that made the process that reads it crash. The main process depends on said process, and all the chain failed.

    Things to improve:

    • make the pipeline more resilient, if you have a “bot detection module” that expects a file,and that file is malformed, it shouldn’t crash the whole thing: if the bot detection module crahses, control it, fire an alert but accept the request until fixed.
    • Have a control of updated files to ensure that nothing outside of expected values and form is uploaded: this file does not comply with the expected format, upload fails and prod environment doesn’t crash.
    • Have proper validation of updated config files to ensure that if something is amiss, nothing crashes and the program makes a controlled decision: if file is wrong, instead of crashing the module return an informed value and let the main program decide if keep going or not.

    I’m sure they have several of these and sometimes shit happens, but for something as critical as CloudFlare to not have automated integration tests in a testing environment before anything touches prod is pretty bad.











  • The famous bad flicker or ghosting of frames is a famous issue in Wayland caused by the desynchronization of frames. Around 2 years ago they patched the driver to let the system tell it explicitly how to sync the frames, and most Linux systems should have the drivers updated to work as such. Since them I’ve not had any flickering like that. A great example was Dragons Dogma 2, the flickering was insane but fixed by the patch.

    I’ve been in Wayland since KDE 6.0 and I’ve a 3080. I think that’s like 2 years now. And I game A LOT.