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.
If anyone's looking to sandbox network, I've had good experience with pasta [1] networking. I make a pasta+bwrap sandbox and expose only specific services via local sockets to cross the boundary.
I wish I could remove the insert key, but unlike the caps-lock that no application rebinds, insert does get rebound. I wish there was an OS level control "pressing insert by accident should not turn on mangle-my-text-mode".
MMORPGs and games that have many different mechanics might be more prone to it, versus first-person controlled games? In my experience its pretty common.
Games often bind skills or other game mechanics to the function keys.
Anecdotally, I switched from `ctrl+shift+i` to F12 for opening the web inspector due to many websites capturing that keybinding for their own purpose (claude and code editors) if I didn't have a function row I'd have to find an even more arcane hotkey.
They're just a nice set of purpose-undefined keys that you or the application can bind to useful functions.
Do you have a solution for auto-merging conflicting changes? Because I think that's the real difference, editing on a laptop and on a desktop before the sync can occur, can cause data-loss (for my potentially naive use of keepassxc anyway).
I think as compilers got smarter, UB changed somewhat in meaning. Originally the compilers didn't perform such complex analysis, and while invoking UB could break your program, it would still do something reasonable.
As a counterexample, I've been seeing more "safety rejections" from Claude. Unlike search, being unable to ask _anything_ about botulinum, or details about the recent Copy Fail vulnerability (without giving my fingerprints to Anthropic to become a "verified security researcher") we're only just beginning to see the ways LLM can be used to distort information and its availability.
I don't think it's been co-opted? Mirroring the emotions of another person you're actively observing doesn't give you insight into why they're feeling that way. It's just mirroring, but its an excellent starting point for learning. To have empathy, for people you're not actively observing, or for future states of people you are observing, you have to be able to model them first, and then mirror the emotions that the model predicts, which can then update the model. This loop is empathy, its both "experiencing other's emotions" and "the ability to understand and predict".