TehPers

Any website using CSR only can’t have a RCE because the code runs on the client. Any code capable of RSC that runs server and client side may be vulnerable.

From what I’ve seen, the exploit is a special request from a client that functionally lets you exec anything you want (via Function’s constructor). If your server is unpatched and recognizes the request, it may be (likely is) vulnerable.

I’m sure we’ll get more details over time and tools to manually check if a site is compromised.

Got 64GB DDR5 earlier this year. I went to check the price of the kit recently and it’s up to $800. Shit’s insane.

Were those same people who were chased out being charged at both the state and federal level with murder?

601.2e does give a chance for a spell, once announced, to be undone. I’m not sure how relevant it is, but I’d think Seth could weave it in a way to argue the spell, as proposed, was illegal in some manner by making an illegal choice with it intentionally.

601.2e The game checks to see if the proposed spell can legally be cast. If the proposed spell is illegal, the game returns to the moment before the casting of that spell was proposed (see rule 730, “Handling Illegal Actions”).

Personally I don’t care a whole lot about the outcome though. Seems like neither player was bothered, and if they’re happy, I have no issue with it.

I’m not the one recommending it lol.

If I had to guess, it’s to improve page performance by prerendering as much as possible, but I find it overkill and prefer to just prerender as much of the page as I can at build time and do CSR for the rest, though this doesn’t work if you have dynamic routes or some kind of server-side logic (good for blogs and such though).

I think their point was that CSR-only sites would be unaffected, which should be true. Exploiting it on a static site, for example, couldn’t be RCE because the untrusted code is only being executed on the client side (and therefore is not remote).

Now, most people use, or at least are recommended to use, SSR/RSC these days. Many frameworks make SSR enabled by default. But using raw React with no Next.js, react-router, etc. to create a client-side only site does likely protect you from this vulnerability.

I think it also doesn’t help that only 4XX (client error) and 5XX (server error) are defined as error status codes, and 4XX errors don’t even necessarily indicate that anything happened that shouldn’t happen (need to reauth, need to wait a bit, post no longer exists, etc).

Trying to think of what 6XX would stand for, and we already have “Service Unavailable” and “Bad Gateway”/“Gateway Timeout”, so I guess 6XX would be “incompetence errors”. 600 is “Bad Implementation”, 601 is “Service Hosted On Azure”, 602 is “Inference Failure” (for AI stuff), and I guess 666 is “Cloudflare Outage”.

It’s a republic, not a democracy.

(Or whatever people say these days to justify how the legislative and electoral systems are complete trash)

No, and your hostility is out of place. Do you have something against GN?

There are induced comas, but they’re terrible for you and only really used a last resort. Also, the quality of sleep is awful, from what I’ve heard.

This is the actual answer with respect to Cloudflare. Their config system was fucked in November. It’s still fucked in December. React’s massive CVE just forced them to use it again.

More generally, the issue is a matter of companies forcefully accelerating feature development at the cost of stability, likely due to AI. This is how the company I’m at is like anyway.

That’s why your what wasn’t working?

The year before that wasn’t without controversy as well. Not surprised to see NL on the list of countries noping out this year.

30 is assuming you write code for all 30 days. In practice, it’s closer to 20, so 75 tests per day. It’s doable on some days for sure (if we include parameterized tests), but I don’t strictly write code everyday either.

Still, I agree with them that you generally want to write a lot of tests, but volume is less important than quality and thoroughness. The author using the volume alone as a meaningful metric is nonsense.

If it were a systemic issue and they had massive control over my life, I would wish them only the worst. Speaking from experience, of course.

After moving out, once they were out of my life for the most part, that dulled into indifference.

I’d be glad if my dad died.

People seem to struggle to understand this, from my experience. I never personally felt this way about my dad, but I fully understand why my mom does.

This is a classic strategy to get games or microtransactions for cheaper.

Quoting Kohler:

We encrypt data end-to-end in transit, as it travels between users’ devices and our systems, where it is decrypted and processed to provide and improve our service.

I guess Kohler recently learned about TLS? IBM’s response, which is a bit random in my opinion, addresses the idiocy of the E2EE claim lol.

I’d hope they encrypt data in transit? Not doing so would be an incredible, though unsurprising, show of incompetence. Setting up TLS and getting certs is easy these days with LetsEncrypt, and a company like Kohler could even get certs through AWS or Azure or something if they wanted.

I can’t imagine why I’d ever spend money on a camera for my toilet, especially if it includes a subscription fee. That’s a new level of stupid.

TL;DR: React broke the internet.

Well, that, but also Cloudflare went down because they were trying to fix React’s shit.

This is more likely the actual incident report:

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.

Edit: If you like reading