Honestly though we are at the absolute tip of the iceberg.
3/ Here he is demoing access to the #Gmail of a purported key political insider in #Kenya just days before the election.
This tech & tactics is kerosene on the flames of democracy.
4/ “I know in some countries they believe #Telegram is safe. I will show you how safe it is”
Yikes.
Unclear how he is gaining access to these #Gmail & Telegram accounts, but the talk of #SS7 is a good hint.
And yet another reminder: SMS is not a safe second factor.
5/ Great to see mercenary election manipulators exposed. Solid journalism.
Trust me, this is a window into a *much bigger industry* active in elections around the world.
So rare to see it caught.
6/ The fact that so much political activity happens on a handful of platforms makes the tooling for political manipulation really interoperable.
Also radically lowers barriers to entry.
Making mercenary election manipulation scaleable & easy to export.
7/ Of course, we don't know whether these guys have successfully changed the outcome of any election.
The guy here is also pretty clearly boasting & trying to sell.
But the mere fact of mercenary election manipulators running around is damaging, even when they don't win.
8/ Even if mercenary election manipulators don't successfully throw an election (e.g. successfully shift mass sentiment), bots, hacking & turbocharged dirty tricks can distort political culture.
Opposing parties have to adjust.
And the net result is harm to democracy.
9/ UPDATE: @haaretzcom reports the mercenary political manipulators targeted 🇺🇸US politicians.
3/ Poor Arthur. But this is an institutional signal that, ~8 years in, militaries are still allowing enough location-aware devices in that it's a big threat.
Incidentally, the @lemondefr team has now been on the #stravaleaks issue for 3 years! I
UPDATE: @Plaid for AI happened faster than I warned.
We are in a historic transformation around AI agents.
Disruption will extend to the core of your privacy.
Companies know the appeal of agentic AI & are working to lock consumers into ecosystems designed to maximize data extraction.
It's not too late, but it might be soon.
But the thing about transformative moments is that new possibilities often open simultaneously with the risks.
We need to build, experiment with & use good private + open AI tools, local models that respect privacy by default & confidential inference that prevents companies from mining the data they process.
Do that & give us a fighting chance for future that respects our freedom, and our boundaries.
Sleep on the challenge of building openly & we relinquish the playing field to the same companies and dynamics that already degrade our autonomy...only faster & everywhere.
2/ What's the deal with @Plaid?
I find people are dimly aware about something involving connecting banking accounts.
I bet you don't know that Plaid helps themselves to mountains of your financial data in exchange for the convenience.
3/ Basically, by providing 'rails' @Plaid has managed to get an absolutely gods-eye-view on peoples financial behavior.
In real time.
That data is available to other companies. And governments.
YIKES: @perplexity_ai is flexing that they have OS-level access to 100M+ Samsung S26s.
Zero mention of:
Privacy
Security
Encryption
What will Perplexity do with this growing stash of personal data from deep inside Samsung phones? What jurisdictions will it live in? Who will it get shared with?
Here's the thing: Android's current security & privacy model involves sandboxing 3rd party apps from each other. TikTok can't read your private notes, for example.
Sandboxing is good & it narrows the attack surface against your private stuff.
But this #Perplexity integration breaks that baseline sandbox model, making a kernel-adjacent data bridge for Perplexity into your personal stuff.
Will users understand the structural shift in privacy?
Meanwhile, the risk of prompt injection & other attacks against an agentic AI that has OS-level access to personal stuff is also real.
Lots of speed, no signs of caution.
2/ Multiple agents & flows each with their own distinct security & privacy issues and levels of OS-level access to private stuff.
I doubt users have the cognitive spare room to parse privacy & security downsides each time they want to ask a question.