Except for the fact that it is open knowledge to every citizen that crimes are being committed using the information in the SSA database. That, and in my opinion, U.S. District Judge Maxine M. Chesney is a fucking idiot.
A federal judge yesterday barred the Bush administration from launching a crackdown Tuesday on U.S. employers who hire illegal immigrants while she considers a lawsuit by the AFL-CIO that charges that the plan will harm citizens and other legal workers.
The ruling, issued by U.S. District Judge Maxine M. Chesney in San Francisco, prohibits the Department of Homeland Security from starting to mail notices to 140,000 employers about suspect Social Security numbers. The “no- match” letters warn of penalties employers face by having discrepancies in their paperwork.
The order was a victory for the labor federation and the American Civil Liberties Union, which filed suit alleging that DHS is overstepping its authority to enforce immigration laws and is misusing a Social Security Administration database. They allege that the letters are an effort to pressure businesses to fire workers whose documents are flagged and could expose countless immigrant workers — including law-abiding citizens and legal residents — to job discrimination.
Chesney granted the request for a temporary restraining order against the government, saying the court needs “breathing room” before issuing a decision on the DHS plan. She set a hearing for Oct. 1.
How, exactly, someone actually checking your legally issued SS# when you start a job, the one use that the SS# is actually designed and legally designated for, will expose anyone who is in the country illegally to job discrimination is beyond me.
But then again, I’m white, so I must be a racist.
So here you go illegals-to-be: You have, as of today, 27 days to get a job before the fed starts telling employers how to check those fake SS#’s you bought. Get cracking.
As an aside on this matter, not too long ago, my employer discovered that one of our residential collection drivers was not who he said he was. The man, whose true identity is still unknown, had purchased the identity of a legal US Citizen of “hispanic decent” and was one of three people who were not the Citizen who were contributing to his account.
This is very odd, as my employer does full background checks on its prospctive employees that even the NICS people would be impressed with. That this guy made it through shows that he spent a very large amount of money on that identity.
And that SSA folks were sleeping at the computer screen. How one person could work four jobs in three states, all contributing to one account and the folks in DC not catch it is beyond me.
“How one person could work four jobs in three states, all contributing to one SSI account and the folks in DC not catch it is beyond me.”
Not beyond me, bro. It’s because the database user (the SSA) never required any justification or cross-checking routine to be built into their database. A computer will only tell you what you tell it to tell you, but I’m sure you knew that. Based on the above truism about computers, it’s safe to extrapolate that whoever ordered the design of the database was TOLD NOT TO ALLOW A CROSS-CHECK TO BE BUILT INTO IT.
This FUBAR is just one more indictment waiting to be issued by a Second Revolution Court Martial Board.
The IRS could also catch it, by the same means, but they don’t either, and probably for the same reason: they’re either prohibited from doing so by law, or have been told by their bosses (that’d be El Presidente Arbusto and his predecessors) not to do so.
Of course, it’s also quite possible that they noticed and haven’t done anything because ID theft is “out of their lane” to borrow a military phrase. And informing the relevant enforcement agency isn’t in their job description, either, so, like your average lazy .gov drone, they don’t do it.
The IRS will notice it when the tax return you file doesn’tdoesn’t show all the income generated against your SS number.
Rivrdog, I doubt someone told them not to put the cross check in. What likely happened is that when the software was created (way back when) it was a missed requirement. Once the problem was discovered it cost more to fix than the government was willing to spend.
I believe I read somewhere that about 4-5 years ago there was an attempt to redo all the governmental databases and software. But the project cost so much money and the first two attempts failed that the project was scraped. Wish I could remember what magazine I read that in.
I CAN tell you though that a solution exists. We just have to implement it. Kind of like why aircraft don’t use GPS satellites yet to track their positions when the tech exists to do it…