Humans have biases. That's not a good thing, but it's human and it's intelligence.
Filtering out bias moves AI out of the intelligence business and into "artificial manipulation."
I'm OK with that and I don't have a problem with the "artificial" label, but don't call a filtered machine intelligent.
This is a validation for those of us who preach that "artificial intelligence" will not be a thing until a computer gets random and throws a fit, like committing suicide if Facebook is down.
... from Systems Analyst at Mobil Oil (now deceased) to Technology Administrator for two law firms.
I was WAY overqualified and management was impressed with my skill level.
I automated everything I could, working with Novell 3.1 at first, then Windows NT out to Windows Server 2013.
I had more than enough time to play. I was upfront with the managing partner that we both knew I was skilled and ethical. I worked on his stuff at his house, so we were good.
The pay wasn't near what I'd made at Mobil, but I was so glad to take off that fucking suit, stop the insane traveling to attend useless meetings, and I was particularly relieved that I didn't have a goddam pointy-haired boss and working in the Dilbert corporate world.
I retired from the Firm 3 years ago, after an 18-year career, and now I play on my computing devices and post to/.
I am armed because I am free. I am free because I am armed.
What are you armed with? Unless you have a fighter jet, a tank, carpet bombs, aircraft carriers, drones, and arms of that magnitude, you're not going after the government.
That kinda reduces adversarial population to peer group.
While I mostly stayed away from case details, and I certainly agree that class action is a cluster fuck, my examples were intended to illustrate what happens AFTER (or instead of) class action.
In the early days when businesses were transitioning to fire code adoption, those who failed to comply were sued out the ass and punitive damages kicked in.
Those legal matters were one-on-one where juries decided that damage multipliers would be effective in changing behaviour.
Nowadays, fire code compliance is factored into the cost of doing business.
--
Back to the original subject: I predict security will follow the same pattern where direct litigation (I'm with you that class action won't do it) against the data gatekeepers will force businesses to adopt infosec policy/technology as a cost of doing business.
It's great that it worked out for you and your workplace.
In my experience, early on, I helped pull some firms out of the ditch because they were the FIRST to apply server updates (3Com OS/2, Novell, NT, and later).
And some bought empty-promise glitterware from startups that disrupted business.
Now I did sign up for beta lots of times, but that activity was not in series with the revenue stream.
For my personal computing devices, I still don't early-adopt and I advise friend/family/former bosses/coworkers to take a wait-and-see, keeping an eye on the canaries for a while.
Competition for IT jobs being what it is, I sometimes had to make a persuasive argument for hiring/keeping me as opposed to a young'n.
In brief, it went like this:
While recent grads know HOW to do stuff that I don't, I know WHY we shouldn't be doing it.
Business is not a good place to be experimenting by being an early adopter.
In skill comparisons, I got my first computer (TRS-80) in 1978. I speak DOS, lived the digital revolution, saw Windows 3.0 fail -- to be fixed by 3.1 -- helped bring in the first network for Mobil Oil, and grew up with the Internet and social media.
I had the experience that entry-level peeps would get later, at the company's expense.
It worked for 30 years.
I've been retired for 3 years, so I don't know if that approach would work today.
You're talking about compensation to individuals, which I agree is only a small irritant.
I'm talking about litigation that leads to mandatory compliance on a much larger scale.
I've posted this before, but think of fire codes at businesses:
Via litigation, the families of those who died were individually compensated. The injured were provided with health care.
As it became clear that businesses didn't really give a shit, the litigation moved away from individual incidents toward more general solutions aimed at prevention.
The fire code compliance ordinances for businesses, with periodic inspections, was driven by litigation.
Data security liability is taking a similar trajectory.
Fire code implementation did not happen until a critical number of people suffered serious harm.
Data security is becoming more of a problem and we have reached an unacceptable threshold of pain.
Where the answer is, "litigation," why do businesses have fire codes that include extinguishers, sprinklers, exits, occupancy limits, construction firewalls, material codes, and regular inspections?
Where the answer is, "litigation," why is asbestos no longer allowed in buildings and why do asbestos companies continue to pay for health care?
Where the answer is, "litigation," why is silicosis a declining disease because of OSHA regulations and why are industries continuing to pay for health care?
There are other examples.
Businesses don't give a flying shit about consumer well being until mitigation moves from the "cost of doing business" to "fuck, look at the expense of litigation."
During my "Munich," I asked the "cloud" vendor about patches to the virtual server, updates to the software (Office and stuff), and they said the Firm was responsible for all that stuff.
The "Firm," was that lead lawyer who didn't know bullshit from wild honey about systems.
Your post makes a lot of sense and I do appreciate that you speak from experience.
Your use of "cloud," triggered a memory of a related issue: One of my firms bought into the "cloud," buzzword.
They bought a cloud service without my input. They told me to help port all of our stuff to the cloud and then they would be reducing my hours, as outsourcing support and services increased.
I just kept my mouth shut and faithfully and ethically did as my management directed.
After the migration (several months), we lost a document.
We're law and the document was majorly critical.
As they had for years, management came to me for retrieval.
I told them to "see the cloud people," as I stirred my coffee.
They told me to make the call.
Because the cloud peeps did not want to be inundated with support calls, they had designated one person as the single point of contact for support.
It wasn't me.
Long story short: Management came to me and asked me what the hell was going on.
I said, "You put everything in the cloud and I have nothing here on the ground."
"I'm useless in this matter."
Then they told me, "Implement Plan B."
I told them, "Your Plan B is Plan A."
The shit hit the fan and, in a conference room with all the lawyers who bought that cloud crap, I told them, "Y'all went behind my back and did something I would have not recommended. You're between a rock and a hard place, but it's your rock and it's your hard place."
We reverted back to in-house servers and stuff, at great cost.
Slashdot Mirror
Cryptocurrency mining?
I never meta comment I didn't like.
... protect its product(s) from bad press.
That's on them.
I'm not the least interested in the welfare of a business located in Russia.
"Innocent until proven guilty" is a USA concept.
Kaspersky is located in Russia, so they have no standing in that regard.
I used the software for years at a law firm as a first line of mitigation for virus infection on desktops.
It worked great.
Then, I'd do a deep uninstall it using Revo Uninstaller because ... Russia.
That was years ago and virus no longer presents a hazard.
Nowadays, the bad stuff is ransomware.
I'd buy a copy of Kaspersky and not install it if it's a ticket to getting the pussy-grabber and his insane cronies out of office.
You said:
You're only getting all hot and bothered because it's about some topic you care about ...
I said:
I'm OK with that ...
My point is that some humans are bonkers. We don't want that, so we "fix," the bonkiness in computers and not in humans.
Batshit crazy AI fanbois are ignoring the definition of, "intelligence."
We are talking about human intelligence, which has its warts.
We sure as hell aren't talking about duplicating the intelligence of a goddam sunflower.
... the "intelligence" is that of a human.
Humans have biases. That's not a good thing, but it's human and it's intelligence.
Filtering out bias moves AI out of the intelligence business and into "artificial manipulation."
I'm OK with that and I don't have a problem with the "artificial" label, but don't call a filtered machine intelligent.
This is a validation for those of us who preach that "artificial intelligence" will not be a thing until a computer gets random and throws a fit, like committing suicide if Facebook is down.
... from Systems Analyst at Mobil Oil (now deceased) to Technology Administrator for two law firms.
I was WAY overqualified and management was impressed with my skill level.
I automated everything I could, working with Novell 3.1 at first, then Windows NT out to Windows Server 2013.
I had more than enough time to play. I was upfront with the managing partner that we both knew I was skilled and ethical. I worked on his stuff at his house, so we were good.
The pay wasn't near what I'd made at Mobil, but I was so glad to take off that fucking suit, stop the insane traveling to attend useless meetings, and I was particularly relieved that I didn't have a goddam pointy-haired boss and working in the Dilbert corporate world.
I retired from the Firm 3 years ago, after an 18-year career, and now I play on my computing devices and post to /.
Whatev, but I'm intrigued by your sig:
I am armed because I am free. I am free because I am armed.
What are you armed with? Unless you have a fighter jet, a tank, carpet bombs, aircraft carriers, drones, and arms of that magnitude, you're not going after the government.
That kinda reduces adversarial population to peer group.
A more realistic grok is:
I am armed because you are armed.
Companies have standards of employment that essentially say, "You fuck with our revenue stream, we're gonna shitcan you."
That's precisely how I discard old iPhones.
I hit them with a sledge hammer.
The battery gets HOT.
I throw the beat uo phone in a bucket of water for a few days.
... was "pencil."
We do agree, mostly.
I spent most of my career working for law firms.
While I mostly stayed away from case details, and I certainly agree that class action is a cluster fuck, my examples were intended to illustrate what happens AFTER (or instead of) class action.
In the early days when businesses were transitioning to fire code adoption, those who failed to comply were sued out the ass and punitive damages kicked in.
Those legal matters were one-on-one where juries decided that damage multipliers would be effective in changing behaviour.
Nowadays, fire code compliance is factored into the cost of doing business.
--
Back to the original subject: I predict security will follow the same pattern where direct litigation (I'm with you that class action won't do it) against the data gatekeepers will force businesses to adopt infosec policy/technology as a cost of doing business.
Right now, they don't have that incentive.
It's great that it worked out for you and your workplace.
In my experience, early on, I helped pull some firms out of the ditch because they were the FIRST to apply server updates (3Com OS/2, Novell, NT, and later).
And some bought empty-promise glitterware from startups that disrupted business.
Now I did sign up for beta lots of times, but that activity was not in series with the revenue stream.
For my personal computing devices, I still don't early-adopt and I advise friend/family/former bosses/coworkers to take a wait-and-see, keeping an eye on the canaries for a while.
wiseguy
Thanks.
... I've some experience with this.
Competition for IT jobs being what it is, I sometimes had to make a persuasive argument for hiring/keeping me as opposed to a young'n.
In brief, it went like this:
While recent grads know HOW to do stuff that I don't, I know WHY we shouldn't be doing it.
Business is not a good place to be experimenting by being an early adopter.
In skill comparisons, I got my first computer (TRS-80) in 1978. I speak DOS, lived the digital revolution, saw Windows 3.0 fail -- to be fixed by 3.1 -- helped bring in the first network for Mobil Oil, and grew up with the Internet and social media.
I had the experience that entry-level peeps would get later, at the company's expense.
It worked for 30 years.
I've been retired for 3 years, so I don't know if that approach would work today.
You're talking about compensation to individuals, which I agree is only a small irritant.
I'm talking about litigation that leads to mandatory compliance on a much larger scale.
I've posted this before, but think of fire codes at businesses:
Via litigation, the families of those who died were individually compensated. The injured were provided with health care.
As it became clear that businesses didn't really give a shit, the litigation moved away from individual incidents toward more general solutions aimed at prevention.
The fire code compliance ordinances for businesses, with periodic inspections, was driven by litigation.
Data security liability is taking a similar trajectory.
Fire code implementation did not happen until a critical number of people suffered serious harm.
Data security is becoming more of a problem and we have reached an unacceptable threshold of pain.
... and IMO hardly comparable to "drones"
Your opinion is not relevant when there are facts.
The drone, of all sorts, types, configurations, for non-military use is an innovation that will have impact and sales far beyond 2021.
Easy on the trigger, OK?
Where the answer is, "litigation," why do businesses have fire codes that include extinguishers, sprinklers, exits, occupancy limits, construction firewalls, material codes, and regular inspections?
Where the answer is, "litigation," why is asbestos no longer allowed in buildings and why do asbestos companies continue to pay for health care?
Where the answer is, "litigation," why is silicosis a declining disease because of OSHA regulations and why are industries continuing to pay for health care?
There are other examples.
Businesses don't give a flying shit about consumer well being until mitigation moves from the "cost of doing business" to "fuck, look at the expense of litigation."
Data security is on the same trajectory.
Litigation is the answer, apparently:
Equifax Hit With 'Dozens' of Lawsuits from Shareholders and Consumers -- Plus a Possible Class Action
Chatbot Lets You Sue Equifax For Up To $25,000 Without a Lawyer
... and, you're welcome.
... announced long ago by FAA.
The drone industry has more money than tobacco and gun combined.
They will be ubiquitous. CNN is the test case.
They floodgate are open.
When I mod, I judge whether the Gentle Reader would benefit from reading shit posts like yours.
-1 Offtopic, Irrelevant, Troll, Flamebait
Fuck you and your claim of censorship and your tribalism, asshole.
I hear ya.
During my "Munich," I asked the "cloud" vendor about patches to the virtual server, updates to the software (Office and stuff), and they said the Firm was responsible for all that stuff.
The "Firm," was that lead lawyer who didn't know bullshit from wild honey about systems.
Your post makes a lot of sense and I do appreciate that you speak from experience.
Your use of "cloud," triggered a memory of a related issue: One of my firms bought into the "cloud," buzzword.
They bought a cloud service without my input. They told me to help port all of our stuff to the cloud and then they would be reducing my hours, as outsourcing support and services increased.
I just kept my mouth shut and faithfully and ethically did as my management directed.
After the migration (several months), we lost a document.
We're law and the document was majorly critical.
As they had for years, management came to me for retrieval.
I told them to "see the cloud people," as I stirred my coffee.
They told me to make the call.
Because the cloud peeps did not want to be inundated with support calls, they had designated one person as the single point of contact for support.
It wasn't me.
Long story short: Management came to me and asked me what the hell was going on.
I said, "You put everything in the cloud and I have nothing here on the ground."
"I'm useless in this matter."
Then they told me, "Implement Plan B."
I told them, "Your Plan B is Plan A."
The shit hit the fan and, in a conference room with all the lawyers who bought that cloud crap, I told them, "Y'all went behind my back and did something I would have not recommended. You're between a rock and a hard place, but it's your rock and it's your hard place."
We reverted back to in-house servers and stuff, at great cost.
That was my "Munich."