I do agree it's a non-problem at this stage. If bunches of other plutocrats head for Mars, then it's time to complain. There are plenty of real existing problems to complain about before ranting at plots from The Jetsons.
Better we test space with dare-devil plutocrats than poor chimps, anyhow. (Also send politicians, lawyers, and Comcast executives.)
That doesn't change the problem here I don't believe. It probably wasn't database injection, but PHP injection. It's not the "storage", but the processing (in PHP) that caused the problem here.
I don't understand why emails are not more often stored as one-file-per-message, with a time-stamp as the start of the file name (YYYY-MM-DD etc.).
Some file systems are wasteful for lots of small files by padding actual space into large discrete chunks, but they should remedy that rather than stuff all messages into one big file.
Her server actually lasted longer than the one she was "supposed to" use. Contrary to popular myth, the office server was not designed for high-security or anything else special. It probably had lowest-bidder quality, and backups either failed or were lost. (A separate procedure was used for classified stuff.)
Unfortunately, extremists are learning they can create lots of chaos withOUT the grandiose 9/11-style plans, which often leave too many clues to hide. Many had speculated on this shift before, but it looks like it's now happening.
Except I don't think this is actually an SQL injection... it's actually a php object injection...
While I usually remember to sanitize strings, situations often occur where you need legitimate punctuation or character patterns that you didn't or couldn't anticipate up front. It then errors out and makes the developer, me, look bad.
Can one anticipate all legitimate future User-Agent string patterns up front? Who knows what wazoo devices will be invented in the future.
Basically one is weighing an approximately 1 in 100 chance a hacker getting in from an injection attack versus roughly a 1 in 5 chance that scrubbing will create practical problems for legitimate users (considering all the data collected from multiple sources and fields over time).
Preventing the hacker is probably the "right thing to do", but it could hurt ones career in practice as users complain about occasional filter errors.
One is weighing high-occurrence-low-damage events against low-occurrence-high-damage events. Since the worse that can happen to a developer is that he/she gets fired and loses a resume reference, most of the risk falls on the org, not the dev. The temptation is to dump the risk on the org by limiting value scrubbing.
It's a tricky philosophical and ethics decision. Humans generally weigh such based on their wallet, not loyalty to the org (especially since orgs rarely return loyalty these days).
It appears she's more than a documenter, she probably was the first to formulate and author concrete examples of digital computer programming (for a general purpose computer), or at least heavily contributed to it. Nobody is claiming Ada invented a computer.
(By "digital" I mean it's based on discrete values, contrasting with say the ancient Greeks "rope programs" for automating puppet shows.)
Okay, "gas and dust" for short, and NOT stars themselves, for the most part. But what exactly causes the cycles of compression and decompression of gas and dust?
We don't really know that. He taught her how his machine worked, but he was not particularly good at describing how it did actual computations on paper it seems, mixing up mechanical ideas with abstract computation ideas.
It appears they had a back and forth dialog on how to better articulate what it does, and she was the better documentor. Whether that's the first "programmer" or "programming manual writer" is a relatively minor distinction.
She essentially wrote, "Analytical Engine Unleashed" with feedback from Charles.
We don't have all the details of their correspondence, but it appears she viewed the machine in more abstract and practical terms than Charles, in part in order to better promote it. His head was more "in the gears" based on his actual writings.
Perhaps a rough analogy would be that Charles was Steve Wozniak and Ada was Steve Jobs. Jobs "sold" the vision of personal computers, while Ada "sold" the idea of an actual general purpose computer.
It's fairly safe to say that she was the first to document practical programming and uses of a general purpose physical computer.
Unfortunately, you can't really call her the "first programmer,"
Who is then? Her writings seem the closest to what we consider "programming". Iteration, conditionals, and (of course) function calls have existed before that time, but her writings are the first that targeted an actual Turing-Complete computing machine, that I know of, rather than just abstract steps.
Slashdot Mirror
"Novel" is not a novel word. I'd like to see more farfegnugen results.
I still have plenty of Asperger neckbeard jokes left.
I do agree it's a non-problem at this stage. If bunches of other plutocrats head for Mars, then it's time to complain. There are plenty of real existing problems to complain about before ranting at plots from The Jetsons.
Better we test space with dare-devil plutocrats than poor chimps, anyhow. (Also send politicians, lawyers, and Comcast executives.)
Explains his (tinted) tin-foil toupee.
Not quite. Mars would still have one less danger: violent jerks.
True. Using the existing file system to divide by topics and sub-topic also makes a lot of sense.
That doesn't change the problem here I don't believe. It probably wasn't database injection, but PHP injection. It's not the "storage", but the processing (in PHP) that caused the problem here.
Define "sanitize" in this case. What is and isn't a valid user-agent string? (and considering future devices that haven't been invented yet.)
I don't understand why emails are not more often stored as one-file-per-message, with a time-stamp as the start of the file name (YYYY-MM-DD etc.).
Some file systems are wasteful for lots of small files by padding actual space into large discrete chunks, but they should remedy that rather than stuff all messages into one big file.
Her server actually lasted longer than the one she was "supposed to" use. Contrary to popular myth, the office server was not designed for high-security or anything else special. It probably had lowest-bidder quality, and backups either failed or were lost. (A separate procedure was used for classified stuff.)
Example
Next you know, they'll start writing checks to that Nigerian Prince.
Unfortunately, extremists are learning they can create lots of chaos withOUT the grandiose 9/11-style plans, which often leave too many clues to hide. Many had speculated on this shift before, but it looks like it's now happening.
Pony haters will hate.
Good! You don't want angry 4-year-olds, trust me.
Trump had a Tribble transplant.
(Sorry, I can't kick Trump joke habit. Therapy failed.)
I'm using similar tech to sell ISIS fart detectors to the Trump Administration.
ISIS is suing him back: his repairs failed and their pipes leak.
While I usually remember to sanitize strings, situations often occur where you need legitimate punctuation or character patterns that you didn't or couldn't anticipate up front. It then errors out and makes the developer, me, look bad.
Can one anticipate all legitimate future User-Agent string patterns up front? Who knows what wazoo devices will be invented in the future.
Basically one is weighing an approximately 1 in 100 chance a hacker getting in from an injection attack versus roughly a 1 in 5 chance that scrubbing will create practical problems for legitimate users (considering all the data collected from multiple sources and fields over time).
Preventing the hacker is probably the "right thing to do", but it could hurt ones career in practice as users complain about occasional filter errors.
One is weighing high-occurrence-low-damage events against low-occurrence-high-damage events. Since the worse that can happen to a developer is that he/she gets fired and loses a resume reference, most of the risk falls on the org, not the dev. The temptation is to dump the risk on the org by limiting value scrubbing.
It's a tricky philosophical and ethics decision. Humans generally weigh such based on their wallet, not loyalty to the org (especially since orgs rarely return loyalty these days).
It appears she's more than a documenter, she probably was the first to formulate and author concrete examples of digital computer programming (for a general purpose computer), or at least heavily contributed to it. Nobody is claiming Ada invented a computer.
(By "digital" I mean it's based on discrete values, contrasting with say the ancient Greeks "rope programs" for automating puppet shows.)
Shhhh, let them find out the hard way. They deserve the lumps of PHB-ness.
Okay, "gas and dust" for short, and NOT stars themselves, for the most part. But what exactly causes the cycles of compression and decompression of gas and dust?
The key is then how important her additions were. It's my understanding that the original gave few if any explicit examples.
We don't really know that. He taught her how his machine worked, but he was not particularly good at describing how it did actual computations on paper it seems, mixing up mechanical ideas with abstract computation ideas.
It appears they had a back and forth dialog on how to better articulate what it does, and she was the better documentor. Whether that's the first "programmer" or "programming manual writer" is a relatively minor distinction.
She essentially wrote, "Analytical Engine Unleashed" with feedback from Charles.
We don't have all the details of their correspondence, but it appears she viewed the machine in more abstract and practical terms than Charles, in part in order to better promote it. His head was more "in the gears" based on his actual writings.
Perhaps a rough analogy would be that Charles was Steve Wozniak and Ada was Steve Jobs. Jobs "sold" the vision of personal computers, while Ada "sold" the idea of an actual general purpose computer.
It's fairly safe to say that she was the first to document practical programming and uses of a general purpose physical computer.
Who is then? Her writings seem the closest to what we consider "programming". Iteration, conditionals, and (of course) function calls have existed before that time, but her writings are the first that targeted an actual Turing-Complete computing machine, that I know of, rather than just abstract steps.