Like donuts, rage farming content is *designed for dunking.*
To get the perfect dunk, big accounts share the content w/their followers.
Thus, they also get rewarded w/engagement for perpetuating the cycle.
The only winning move is not to play.
Did you Quote Tweet a political ad?
You just donated free advertising.
Would you contribute a particular politician?
No? Then don't QT.
Well, we did it. We got rage farmed into amplifying a disgraced toxic politician into a busy news cycle.
Next step? He'll claim censorship & that he's under attack by democrats.
Then fundraise.
This is an entirely predictable playbook.
Step 1: Everyone watch this bad thing he did!
Step 2: We must drop everything & condemn him.
Step 3: Here's more bad things he did!
Step 4: Wait, why does his stuff drown out things we care about?
Meanwhile, all Twitter's algorithm hears is "SHOW US MORE OF HIM!"
"So, should we ignore it when politicians say extreme things?"
No. We're in dark place & need to fight it.
But we must be smart, especially on Twitter.
That means learning how algorithms 'hear' us.
And making sure we aren't baited into inadvertently platforming our opponents.
Whomever cooked up his rage farming knew exactly what they were doing.
Predictably, he followed up by amplifying critical coverage in the WaPo that... included his video.
Of course, people angrily Quote Tweet that, too.
And so he's done it. And we've helped at every step.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
NEW: @WhatsApp caught & fixed a sophisticated zero click attack...
Now they've published an advisory about it.
Say attackers combined the exploit with an @Apple vulnerability to hack a specific group of targets (i.e. this wasn't pointed at everybody)
Quick thoughts 1/
Wait, you say, haven't I heard of @WhatsApp zero-click exploits before?
You have.
A big user base makes a platform big target for exploit development.
Think about it from the attacker's perspective: an exploit against a popular messenger gives you potential access to a lot of devices.
You probably want maximum mileage from that painstakingly developed, weaponized, and tested exploit code you created/ purchased (or got bundled into your Pegasus subscription).
3/ The regular tempo of large platforms catching sophisticated exploits is a good sign.
They're paying attention & devoting resources to this growing category of highly targeted, sophisticated attacks.
But it's also a reminder of the magnitude of the threat out there...
WHOA: megapublisher @axelspringer is asking a German court to ban an ad-blocker.
Their claim that should make everyone nervous:
The HTML/ CSS code of websites are protected computer programs.
And influencing they are displayed (e.g by removing ads) violates copyright.
1/
2/ Preventing ad-blocking would be a huge blow to German cybersecurity and privacy.
There are critical security & privacy reasons to influence how a websites code gets displayed.
Like stripping out dangerous code & malvertising.
Or blocking unwanted trackers.
This is why most governments do it on their systems.
3/Defining HTML/CSS as a protected computer program will quickly lead to absurdities touching every corner of the internet.
Just think of the potential infringements:
-Screen readers for the blind
-'Dark mode' bowser extensions
-Displaying snippets of code in a university class
-Inspecting & modifying code in your own browser
-Website translators
3/ What still gives me chills is how many cases surfaced of people killed by cartels... or their family members... getting targeted with Pegasus spyware.
The #PegasusProject found even more potential cases in Mexico.