I appreciate the info and the time and effort you took to pass it along. I certainly might get around to using Docker. If you work with node you might be interested in create-api-lite, an npm package (which I haven't used yet) that generates a basic node project structure, including dockerfile.
When you look around at women I think the major difference between creepy vs not creepy is whether you're furtively and ineffectively trying to hide it vs smiling and being open. If a woman notices you looking, to smile and maybe give a little nod before looking away is friendly. Fearfully glancing away and then sneakily looking back is creepy. And if she acknowledges your smile and nod with a smile and nod of her own, it might indicate a bit of interest. Or not. But you have to let go of the idea that you're peeping out through the window blinds afraid of the world, and since this is bothering you so much I would strongly suggest looking into a little therapy.
This phenomenon was around eons before LLMs. You have to figure out how conditions are different when the problem happens in the wild and when you fail to duplicate it.
You wouldn't - what they're describing is called "SQL injection" - a way to fool poorly written web server code (regardless of what language it's writen in) into executing SQL code. The poorly written server code takes what's entered in a form field on a web page and pastes it into a skeleton of a SQL statement - in this case the text in the input field is SQL that ends the intended statement, followed by a new statement that deletes a table. For this to even work, the SQL skeleton on the server would have to be structured in just the right way so the modified version with the pasted-in text still makes sense. For this reason, hackers attempting SQL injection usually have to do a lot of trial and error to get something to happen. The only way it can work at all is if the server software handling the web page sends SQL commands to a database server as text, as if they're being typed in, and the server executes them. You can't inject C in this way because unlike SQL, C code isn't just executed, C programs have to be precompiled.
I love how things like this develop a mystique. The KFC eleven herbs and spices, supposedly on a two-part list kept in separate vaults. The handwritten recipe for Coca-Cola, transported under heavy guard to a new vault in 2011. Donald Trump's hair elixir formula, kept secret by Epstein until his prison cell suicide during a coincidental random camera malfunction. The list goes on...
This has been a trope forever, but is it really still common? I usually get into a room within a few minutes of my appointment time. Then a tech takes my vitals and collects other info - which is part of the appointment and the doctor doesn't need to be there for it. Then a few minutes later the actual doctor shows up. I haven't timed it but it's not annoyingly long.
The need for a constant signal to scan movement is a good point. Makes sense that nearby wifi devices can't just be sitting there, they have to be actively transmitting to the router or there's no signal for the target to interfere with. I must have gotten CSI and wifi scanning confused. Tbh I'm not even sure why CSI is in the article except for history, but I found the principle fascinating. In your research did you turn the intererence into anything like a heat map of a person standing in the room, or is it more of a signal fingerprint, like chromatography or spectrography?
I can totally believe when it tracks a person it can tell when the same person walks by again later. But matching people with their actual identities would require a database of wifi scan data that simply doesn't exist yet.
I appreciate the info and the time and effort you took to pass it along. I certainly might get around to using Docker. If you work with node you might be interested in create-api-lite, an npm package (which I haven't used yet) that generates a basic node project structure, including dockerfile.