Let’s be clear: these data dredging requests by Treasury will result in violent attacks on crypto users.
Why? Because Treasury got hacked and can’t secure their data. Lists of home addresses of crypto users will keep leaking, as they did with Ledger. And criminals will use them.
The idea of forcing companies to surveil millions of people — and then getting the database leaked on the internet — is a scenario beyond what even @Snowden envisioned.
To “protect” you from crime, they (predictably) give data to criminals.
Treasury’s hacks will cause violent attacks.
Until they can prove to an external auditor that they can secure their data, which will mean a multi-year hack-free period, they must stop asking for data that will predictably leak to criminals.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
90k households reportedly left SF this year, out of about 360k total.
Voting with their feet against poop, needles, car break-ins, fires, power outages, housing shortages, dysfunctional schools, physical assaults, exorbitant costs, and all the rest.
Point being: the exodus is real, as are the problems. Don’t let anyone tell you they’re not.
The silver lining is: SF will never get its monopoly back. Neither will Silicon Valley writ large.
Tech was overconcentrated, and decentralization was overdue.
Note: I thought the numbers were huge, which is why I included cites. It’s possible the 2 definitions of households don’t exactly match, or that in-migration has partially offset loss. More analysis welcome.
Start by sketching out the frontend and backend as normal. Then replace a few key backend calls with reads and writes to a decentralized database, namely a blockchain. balajis.com/yes-you-may-ne…
In other words, you don't need to throw out everything you know about web or mobile development. And you can often still use a standard DB as the data store for much/most of your app.
But for certain key functions, like sending/receiving funds, that's an on-chain operation.
Anyone who's built anything over the last decade is familiar with the concept of using multiple databases. At a minimum, you have your main Postgres plus a data warehouse or the like for analytics.
That's the consequence of software eating the world. Everything becomes analogous to a PDF, a set of digital instructions that you can get a printer (or a robot) to print out in the real world.
Amazon Prime, drop shipping, food delivery, ride-sharing...all of them involve a digital frontend and a human backend.
But over time more pieces are getting automated. Robot manufacturing, autonomous trucks, drone delivery, self-driving cars. So the backend goes digital too.
AI (in general) and virtual influencers (specifically) are obvious examples of this trend, where the manual backend is no longer as necessary. As is crypto, where much of the labor in the financial system is being automated with smart contracts and digital signatures.