webstrand

That doesn't justify its deletion, it might justify warning the user, but unconditionally deleting data not owned by the app shared with other apps?

I didn't read it as dismissive. I think the "Why doesn't this work?" at the end is key, implying they know they're probably wrong, but don't know why. It's pretty common to form and present hypothesis like this, hoping that anyone who knows the actual theory can easily provide a counterexample showing why it's wrong. It's not at all intended to be dismissive.

Usually its me who has been committing with a bogus email address, because I don't like having my real user/email set in my $HOME/.gitconfig

ES6 class syntax is still mostly just syntax sugar overtop prototypical inheritance.

JS _does_ still have TCO (called Proper Tail Calls), Safari's JavaScriptCore implements it, and is technically the only conforming interpreter.

I'm using linux, and I got access with no issue. CF is having an issue.

I also do this, except 7.0.0.0/8 instead. Its great for not conflicting with hotel wifi dhcp.

Class D amplifiers use that same trick, just at much higher switching frequencies (pushing quantization noise ultrasonic, where it can be filtered). Since transistors are most efficient when fully on/off, very little power is wasted as heat. That's what made the modern revolution in tiny amps possible.

Interesting, could it be mitigated by the server doing its own prediction and defogging the peeker early? Or is lag prediction in CS2 not entirely client-sided.

That doesn't sound at all like any ORM I've ever used. I've struggled in the past because The ones I've used are actively hostile to laying out data in the database in a way not proscribed by the ORMs philosophy. Heck of the ORMs I've used, one didn't support parameterized joins and the other didn't support joins at all.

---

It's not usually a DB guy gatekeeping, it's that multiple apps use the same database so layout changes are costly.

Web fiction, freely produced and distributed by "consumers" already existed prior to 2019. There are thousands of novels you can read that people produced for their own enjoyment, some even managed to make money off of it via patreon or Amazon's Kindle direct publishing.

Isn't CSRF about forging mutating requests? CORS doesn't block the underlying GET/POST request, the request still goes through and the server still needs to properly implement CSRF prevention. CORS just prevents javascript from reading the response.

CORS _additionally_ requires OPTIONS pre-flight to succeed, before allowing any kind of request outside of what can be achieved with a HTML form submit action. So it blocks PUT/PATCH/DELETE, specifying most Content-Type, and specifying nearly all other headers. But this is just blocking "non-standard complex requests that might confuse badly programmed pre-javascript-era servers".

It passes all standard requests that you could have made by: embedding the url as an image src, the target of a HTML form, endpoint for csp reports, etc. All still need to be checked methodically by the server for CSRF if it's going to take any mutating action due to the request.

I don't actually know of any? I've long since removed the key from my keyboard, and haven't come across anything that actually used it. What games?