1283
The government doesn't use SQL
(programming.dev)
See the post on BlueSky: https://bsky.app/profile/provisionalidea.bsky.social/post/3lhujtm2qkc2i
According to many comments, the US government DOES use SQL, and Musk is not understanding much what's going on.
I'm sure folks on here know this, but you know, there's also that 10K a day that don't so...
What makes this especially funny, to me, is that SSN is the literal text book example (when I was in school anyway) of a "natural" key that you absolutely should never use as a primary key. It is often the representative example of the kinds of data that seems like it'd make a good key but will absolutely fuck you over if you do.
SSN is not unique to a person. ~~They get reused after death, and a person can have more than one in their lifetime (if your id is stolen and you arduously go about getting a new one).~~ Edit: (See responses) It seems I'm misinformed about SSNs, apologies. I have heard from numerous sources that they are not unique to a person, but the specifics of how it happens are unknown to me.
And they're protected information due to all the financials that rely on them, so you don't really want to store them at all (unless you're the SSA, who would have guessed that'd ever come up though!?)
It's so stupid that it would be hilarious if people weren't dying.
Thanks for (starting to) explain this concept to people not accustomed to how the US does their shit.
See, where i live, we used to have for example a Tax-Number. That was a thing the taxdepartment used to identify a person. But if you move from city a to city b, that numbers changes. So if you move a lot, you will have numerous of these.
Now, some 15 years back, the Tax-ID was introduced (fellow residents at this point will lnow it might be Germany) and this number is a one-in-a-kind ID that will only be assigned to you. They create it shortly after birth. My sons first registraion ID was this, before anyrhing else. You will also get a uniqie healthcare-ID that also works like that.
So...how does that work in the US and why is habing a changing number that is not unique helpful? Or what is Elon not getting? I dont get it either because I dont know how this works for you.
Thanks in advance to shed light on this.
It doesn't. There is no truely unique ID in the US.
Source: myself. Worked on health insurance and it was hell.
It's wild too. I've been in the hospital a lot lately and in addition to a bar-code wristband, every healthcare worker, before doing anything with me (the patient) will ask my full name and either birthday or address and then double-check it against the wrist band. This is to make sure, at every step, that they didn't accidentally swap in some other patient with the same name. (Not so uncommon, lots of men have their father's name.)
Meanwhile in like Iceland, everyone gets assigned a personal GPG key at birth so you can just present you public cert as identification, not to mention send private messages and secure your state-assigned crypto-wallet. Not saying such a system is without flaw but it seems a lot better than what we're doing!
You want them to do that regardless of the how the country keeps track of individuals. The point of all that asking is to make sure they have the right patient for the right procedure.
You don't want to have something amputated or removed unless you have to.
This has happened many times. In the last city I lived in, a man went in to have a leg amputated and they got the wrong one, so he ended up with zero legs.
This is a joke right? I really really hope that they aren't trusting randoms to know how to manage a gpg key properly.
It's hard enough to get people actually interested in it to do it correctly.
And using gpg to constantly identify yourself would mean needing to keep multiple copies of your private key all over the place. I find it unlikely that regular people are issuing new keys and revocation certs properly. Not to mention having canonical key servers (maybe the government could manage that, but the individual is responsible for maintaining a way to get the canonical most up to date key)
Using gpg backfires because if you lose access to the key or it's compromised (say by putting it on your phone) you lose everything. They work for people who know what they are doing because you are supposed to issue keys for specific tasks and identities, but there is just no way that that is happening.
I'm being sarcastic but not by much. Nordic countries do have much better digital id systems and the EU overall looks to be following their model.
https://www.mitid.dk/en-gb/get-started-with-mitid/
https://www.openbankingexcellence.org/blog/eid-and-the-eu-digital-identity-frameworka-scandinavian-perspective/
This is the first I've heard something like that about Iceland; but I do know a little bit about Icelandic personal ID numbers.
When you die your social is reused and assigned to someone else eventually. This is what makes it not unique. If something were to screw up in the process the new person could have debt from the prior person for example even though it is not their debt. Another concept common is using the last 4. There are so many conflicts when using just last 4 in a database its bad design.
This is not true, but often repeated. From SSA
https://youtu.be/Erp8IAUouus explains it pretty well
Came here looking for Grey, was not disappointed.
Thank you!