Huh, what would be the goal of connecting this database to an API on or near doge.gov? Surely it's not the "actual"/"source of truth" database, more likely a copy: I can imagine the geniuses thought ""let's mirror everything online on a single system so it's easier for all of us to access it and do queries like "WHERE gender NOT IN ('m', 'f') OR race NOT IN ('white')" and get results from all the databases we know of."". (I assume there is no single federal employee database?)
And since the truth is whatever they say nowadays, maybe it IS the "source of truth" database.
Yawn.
https://en.wikipedia.org/wiki/Joke
Yawn indeed.
This logic only holds if they’d have knowledge about websites, as opposed to other topics.
There’s many SDEs with long careers who would make security mistakes on websites, yet nonetheless are tech experts.
Would like to see a source on this.
Governments are similar to large enterprises whereby every bit of code going into Production requires a full security, architecture and site reliability review.
There is no doubt bugs in bespoke web applications but for your typical website.
All you had to do was actually read the article; it’s the very next paragraph from the one I quoted.
What data are you basing this on? Federal websites have an approval process which includes a security review so I’d expect some familiarity with that in your response.
Citation?
Hope they used good proxies, because this seems like a felony.
> One of the sources told 404 Media that they were able to push updates to a database of government employment information after studying the website’s architecture and finding the database’s API endpoints.
Oof, not something to put in your article.