Early 90s... an explosion at a chemical plant that made an Epoxy Resin used int he manufacture of IC chips, in particular DIP chips used for RAM at the time.
The immediate response was that the price of RAM (and no other chips) TRIPLED in price over night.
The problem was... the resin cost $6/lb and never increased in price. Sumitomo had a 6 month stockpile untouched by the explosion. Companies that made use of the resin pellets for RAM production also had 6~12 month stockpiles. In fact, they weren't even scheduled to produce any of the resin for months.
Needless to say, the production resumed long before there was any real shortage, but prices did not fall until systems required a magnitude greater level of RAM.
Later, we saw a flooded Thailand that somehow crippled hard drive production... again, an artificial jump in prices that has never really returned to reality.
Big tech manufacturers and their distributers will always seek to turn crises into money machines.
Strikes again....
THIS. "City of London" is a single square mile, and is exclusively run by corporate entities as part of some centuries-old tax evasion scheme. The police are a joke, and funded to only look after their corporate masters' interests, without regard to moral and ethical grounds.
Well, looking at the error now, I guess it was specifically an issue with her last name, and probably something generically taking the serialized data and changing "True" to true without consideration for the data type.
Ugh.
Anyway, either they are really bad at writing validation code for the serialized inputs, or transforming the serialized data in some attempt to clarify the field values, which is dumb when done with no awareness of types ahead of the transformation (changing quoted True to unquoted true, assuming it's a boolean value and your non-standard serialization format requires an unquoted true to interpret as a boolean value - the transformation code makes the assumption that the input is improperly formed because it does not know the real field type, and only assumes it)
Sorry, but "racheltrue@icloud.com" has no delimiters that might mess with a concatenated query, and definitely would not affect properly sanitized, delimited, quoted string parameters for a SQL query.
I would have to see the code to understand how this could mess up validation for her login. Using an IndexOf or Contains for "true" makes no sense, in any context, either. I can't fathom even a bad coding scenario where that might happen.
On the other hand, if it had to be coded in one of Apple's non-industry standard language de jours, I suppose there could be some room for massive fail.
Simple enough solution... block all links to "media outlets" who demand payments. Block them globally. Don't negotiate. Don't legitimize the ridiculous law.
Let's see how long they last before demanding the laws be changed.
What is "IT" anyway? Seriously
Apparently, something that died in 2020.
For my company, everything in our IT grew. NetOps people found their VPN systems tested and expanded capabilities greatly. Security grew... and we brought on more developers (all of them contractors) for the incredible growth we saw due to the challenges brought on by dealing with COVID and the lockdowns (and how it affected our business).
There was no "death of IT" and anybody who predicts this, then claims they are right is insane.
...a stone and steel multistory building with a very beefed up cellular network, augmented by wifi with triangulation/location capabilities and logging (which means they can easily track those rioters with cell phones regardless of their posting, as long as it was on).
Then again, we could say "wake up sheeple" and again question whether jet fuel can melt steel, too.
I'm sure your intention was not to stir up the more conspiracy minded, but if it was, your username checks out, I guess?
Numeric stability is probably not all that important when you're guessing.