Cloudflare DDoSed itself with React useEffect hook blunder (www.theregister.com)
from TheBat@lemmy.world to technology@lemmy.world on 18 Sep 12:45
https://lemmy.world/post/36100835

#technology

threaded - newest

eager_eagle@lemmy.world on 18 Sep 12:52 next collapse

glad to know it’s not just me

ozoned@piefed.social on 18 Sep 14:24 next collapse

The DDoS came from … INSIDE THE HOUSE!

Passerby6497@lemmy.world on 18 Sep 15:03 next collapse

Finally, a DDoS that even Cloudflare couldn’t stop

aeronmelon@lemmy.world on 18 Sep 15:53 collapse

CloudFlare stopped the DDoS by destroying their own servers.

“I’ve won, but at what cost?”

hume_lemmy@lemmy.ca on 18 Sep 15:59 collapse
sp3ctr4l@lemmy.dbzer0.com on 18 Sep 16:08 next collapse

Remember, always, immediately, push new updates to prod, specifically right before you go home at the end of the day.

xianjam@programming.dev on 18 Sep 17:23 next collapse

We’ve all done it. …right?

silt_haddock@lemmy.world on 18 Sep 17:46 collapse

Bonus points if you do it the day before you leave for vacation!

Armand1@lemmy.world on 18 Sep 17:04 collapse

I recently ran a session and wrote an internal blog post about why useEffect was a dangerous crutch that should be avoided wherever possible. This was due to complicated logic and unexpected interaction bugs.

This is a little different but I still feel vindicated.