It is VITAL that you understand we got here because we allowed Fox News, Newsmax, Alex Jones, Brietbart and MANY MANY others to create a siege mentality in the right.
One of the most disturbing aspects of a siege mindset is a willingness to reflexively believe ANY claim against
More from Pam Keith, Esq.
More from News
I'm hesitating to read or listen to this for fear it oversimplifies. I worked for about a year @NYPDnews on this. We learned a LOT. Most of the $320 million I estimate was lost by New Yorkers on Cyber-enabled scams in 2019 began with voice calls to set the hook...
Looking through our empirical data, we see that scam calls dominate the world of Cyber-enabled (which doesn't include ransomware or network intrusion/takeover, but does include crime that leverages a digital channel for some aspect of the attack).
We found that NYPD officers, when empowered to combat this kind of crime with training and tools, were champing at the bit to get out there and fight it. They all know the scams are out there - many told us of family members who'd fallen victim - but they felt powerless to act...
I personally blame the Feds, who over the past two decades have worked hard to make all "Cybercrime" seem (a) mysterious and sophisticated to the extent that (b) only the Feds could combat it, through tools like the IC3 survey. That tool is actually quite ineffective.
As I said at RSA2020, for Cyber-enabled scams, IC3's survey is the place where good leads go to die. For example, in 2018 around zero point three three percent of cases reported to it were ultimately investigated by a task force. They're just snowed under. https://t.co/IxjM6t0cfm

Looking through our empirical data, we see that scam calls dominate the world of Cyber-enabled (which doesn't include ransomware or network intrusion/takeover, but does include crime that leverages a digital channel for some aspect of the attack).

We found that NYPD officers, when empowered to combat this kind of crime with training and tools, were champing at the bit to get out there and fight it. They all know the scams are out there - many told us of family members who'd fallen victim - but they felt powerless to act...
I personally blame the Feds, who over the past two decades have worked hard to make all "Cybercrime" seem (a) mysterious and sophisticated to the extent that (b) only the Feds could combat it, through tools like the IC3 survey. That tool is actually quite ineffective.
As I said at RSA2020, for Cyber-enabled scams, IC3's survey is the place where good leads go to die. For example, in 2018 around zero point three three percent of cases reported to it were ultimately investigated by a task force. They're just snowed under. https://t.co/IxjM6t0cfm

You May Also Like
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x

PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ

The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.