Part of the Social Security website (ssa.gov) only works during certain hours
Part of the Social Security website (ssa.gov) only works during certain hours
Archaic hardware and software requiring downtime on the backend to do standard maintenance like backups, software changes, changing vacuums tubes, pulling moths out of relays.
As opposed to modern hardware and software architectures that allow for standard maintenance without downtime.
The excuses vary (taking systems offline to run archaic batch processing, pretending to want to protect jobs by not having machines outperform workers, etc.), but the bottom line is that a certain political faction deliberately writes stupid rules like this as sabotage in order to prove that government doesn’t work.
It’s the same sort of reason why the local license plate office charges a “convenience fee” to renew your tag online even though it costs the public less than paying a clerk to process it in person.
Not really. The real answer is that different parts of the federal government are underfunded or overfunded according to political ideology and expedience. This is a great example; the SSA is underfunded while the military is overfunded which results in clear performance differences.
You’ll never hear a conservative bitch about the US military saying that it can’t do anything right, and it’s like, yeah, duh, because it has a huge fucking budget and basically gets anything it asks for.
Social safety net programs? Not so much.
There is a reason and not what you think.
Look here: kbin.social/m/…/639904
Your point is incorrect. It is not needlessly complicated. It has to do with mainframe batch processing times.
It’s not a conspiracy, it is a technical challenge that is not easy to some. It is complicated, but not needlessly. If it was easy, it would have been fixed.
I am sure there are a number of private companies that do the same but simply don’t tell you.
E.g., every bank has a cut off time for transfers, same reason.
That’s how I feel gesturing broadly at the 3 or 4 states they’re still actively fighting against minimum marriage age laws.
Their voters out here voting for them to “protect children” from pronouns, from books, from learning - then turn a blind eye when they vote to make marrying at 12 legal again or to force 12 year olds to give birth or to send 12 year olds back to the mines. Not only are the politicians cartoon villains, in 2023 so are their voters. Full Stop.
Massive frame batch processing is the usual reason.
And before it ask why not replace it, the short answer outs it is complicated.
It might be a question better speed in eli5.
…so it would be stupid if this works, but it’s a stupid problem in the first place, so try changing the time on your computer to be within their operational hours.
I recall cheesing videogames with that back in the day, and the UI of a halfway decent videogame would put most govt web design to shame. Worth a shot?
Come on. If you actually worked for social security you have to know why. It’s is related to mainframe batch processing.
But I can see why you might say what it did. Maybe you think it seems cooler to simply dump on the government it meant your 20 years of experience is 1 year repeated 290 times. So really 1 year of experience but you just got older.
I’m going to have a guess and suggest that the website is probably integrated with some much older mainframe system and a batch process or several batch processes run daily overnight to shuttle data between the two systems to keep them updated and in sync.
Syncing the two sets of data while the database is live and changing is a pain the the bum, so they freeze it while the data transfers are taking place.
This is the real answer. Main frame batch processing.
And till you haven’t experienced it, it seems like an excuse. Why can’t you simply do it all the time. Why can’t you get rid of the mainframe, etc.
But if only it were that easy. There is a reason IBM can still acquire multi billion dollar companies and then run them into the ground.
My company has maybe a couple million customers and can’t get rid of its mainframe and in areas that it’s gotten the process away from the mainframe, batch patronizing is still a thing. Because that is the only way to guarantee integrity.
So yea. I wish your comment gets more up votes. Because it is not a conspiracy, it is a technical limitation.
I had to do some legacy app modernization for one of the largest telecoms companies in the US, and their mainframe system and the UI, while ugly, performed so much faster than the modern approach.
Given, we weren’t the most talented team out there, but rendering the UI on the server side was unmatched in performance versus what we could get out of a web browser. I was the UI guy so I didn’t really touch mainframe side, but it was wild to me that they made this system like 30 years ago and it worked so much better than our modern implementation
It can be, but it’s also an issue of “move fast and break things” doesn’t work in all environments.
You don’t want your bank to have an oops with your checking account, or your medical records to get messed up because someone didn’t code it well enough. If it works and is stable, there needs to be a demonstrable benefit and guarantee that it will keep working when to moving to a newer system. Usually on a budget of “what do you mean you need a budget, just do it”.
… its a website run by the US Government. Why does it have such large downtimes in this day and age?
In case you were unaware, the US government sucks at everything but killing people, and sometimes they take 20yr to do that. They just flat out suck, there’s your “why.”
Most government sites from NY also keep business hours
I asked my family’s lawyer about it and he said that the time open and closed is a law. So they have to “close down” certain sites at certain times to comply with those laws
What exactly does Sabbath mode do? Is it like a burst of deep freeze so the appliance can power down Fri-Sat and stay cold, or what?
Asking as a renter with Sabbath mode on the fridge in my apartment.