La migra app is inside your car. Your data is in the crosshairs.
La migra app is inside your car. Revolut is also leaking your data to fake government requests. These aren't separate headaches — they're the same pressure on the same wallets. The fix is practical: data residency is an infrastructure problem, not a legal one. Get the tools right, and the paperwork follows. Why this matters for us: when the systems that hold our IDs and money shift, we feel it at the border and in the bank.
La migra app is inside your car
The FTC just slapped GM with a five-year ban on selling customer data to consumer reporting agencies and third-party data brokers. For years, the company was collecting all sorts of data—how often you sped, whether you drove at night—and selling it to brok. This is the kind of thing that happens when you buy a car with a screen and don't realize you're also signing up for a data farm.
The ban stops GM from feeding that data into the credit and risk systems that decide who gets a mortgage, who gets an insurance rate, who gets flagged. It's the same architecture as the border surveillance feeds—your movements, your patterns, your habits—packaged and sold. The only difference is the fence is digital now.
Why this matters for us: the brokers don't care about our neighborhoods or our names; they sell our data to whoever needs it, and the ban only covers GM. If your car is a Chevy, it's safer now. If it's a Ford, a Toyota, or a Tesla, the data's still out there selling.
Revolut gets hit by fake government requests — your data is in the crosshairs
Revolut confirmed customers were scooped up by a data breach that came through the back door: fake government requests. Instead of a brute-force hack, someone forged official-looking demands and got the bank to hand over account data. The company said it notified affected customers and flagged the relevant government agency, law enforcement, and financial regulators — so the fix is already underway.
What makes this one worth paying attention to is the method. The la migra and other agencies send requests by the thousands. It's easy for a phony request to slip past. The trick is getting the right paperwork to look right. Once that's done, the data flows.
Why this matters for us: if you bank with Revolut, your account info was taken — and the lesson is real for every one of us who relies on a single app to keep our money, our IDs, and our records in one place.
The best security folks write rules in plain English, not in jargon.
— franklyspeaking.substack.com
#how-to-be-a-security-person-who-doesn-t-get-in-the-way-64864eData residency is an infrastructure problem, not a legal one
Data residency is the rule that says where your data lives depends on your laws, not on your servers. Some regions require data to stay in-country; others don't. The law changes. The wires don't.
The real problem is infrastructure design. Where does your database live? Who backs it up? Can you move it when the rules shift? The legal team writes the policy. The engineers build the plumbing. If those two don't talk, you're paying for a rule you don't need or missing one you do.
Fix the plumbing first. Put the data in a region you control. Keep the backups close. Build the routes to move it without rewriting everything.
How to corrupt SQLite — the guide you actually want
SQLite has a how-to-corrupt page that's gone viral for a good reason. It's not a marketing post. It's a checklist written by the people who maintain the engine, and it's practical — the kind of thing you bookmark and come back to when your database starts acting funny.
The page covers the gotchas that bite people: WAL mode and journal files, concurrent access, the difference between page corruption and logical corruption, and the tools you use to check — PRAGMA integritycheck, PRAGMA journalmode, and the dump-and-reload trick. It's not long. It's dense.