Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> A change made to how Cloudflare's Web Application Firewall parses requests caused Cloudflare's network to be unavailable for several minutes this morning. This was not an attack; the change was deployed by our team to help mitigate the industry-wide vulnerability disclosed this week in React Server Components. We will share more information as we have it today.


does this mean we can blame React Server Components for something new?


Listen to the sound of HN hawks erupting with joy when they realize they can blame JS, React, RSC, Rust, Cloudflare, and the cloud all for one outage.


For those hawks, Christmas has come early.


I always suspected RSC was actually a secret Facebook plan to sabotage the React ecosystem now that their competitors all use it to some degree. Now I’m convinced.


I mean RSC wasn’t really even the FB folks as far as I remember, they barely control React anymore


When are they going to figure out that canary deployments are a good idea? Do they just push every change straight to prod globally?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: