Earlier quoted context omitted.
It's uses a simple, purpose-focused template of a type that is a common recommendation for clear communication, outline numbering, and highlights keywords using monospaced text, as is common practice in technical writing. None of that is unusual for a human, especially writing something that they know is going to be high visibility, to do. Modestly competent presentation is now getting portrayed as an "AI tell".
I’m not arguing that it’s unusual for humans to write in this manner, but when you use something like chatgpt with some frequency and see that as a common response template it’s an obvious pattern..
DOGE worker’s code supports NLRB whistleblower
461–470 of 586 posts
Re: DOGE worker’s code supports NLRB whistleblower
#462Earlier quoted context omitted.
In that case, you and departments you work for are either breaking the law regularly or working with public data anyway. Besides, no one needs unmonitored write access for audit. Even less DOGE who does no audit and don't have knowledge how to do audit. Audits are supposed to he traceable.
No one needs write access, but most systems only have a read/write predefined role for tenant-wide access. If you don’t trust the department staff to give you anything but a predefined role, it’s typically the only option. Similarly if you need to fire privileged IT staff on the spot for headcount reduction you need admin-equivalent rights to lock them out. You can’t in general trust disgruntled admins to lock themse…
I find the argument the most absurd in relation to DOGE. There is no reason to give them more trust then to anyone else in goverment ... and multiple reasons to trust them less. Starting from personal histories of some of them and how they were selected.
As such, this "I dont trust" is just reflection of their incompetence, arrogance and a lazy excuse.
Re: DOGE worker’s code supports NLRB whistleblower
#463Earlier quoted context omitted.
> What data in a federal agency could the chief executive not have authorization to access? Personally? For starters, he can't access anything the Legislature's laws say he can't. The Executive is there to implement the law, and that includes obeying them him/her-self. A President telling other people to break the law on his behalf by threatening to fire them is also a crime of extortion.
> he can't access anything the Legislature's laws say he can't. Can the legislature make rules for the president without constitutional amendment? I am interested- I’ll see if I can find examples.
Re: DOGE worker’s code supports NLRB whistleblower
#464Earlier quoted context omitted.
> What data in a federal agency could the chief executive not have authorization to access? Personally? For starters, he can't access anything the Legislature's laws say he can't. The Executive is there to implement the law, and that includes obeying them him/her-self. A President telling other people to break the law on his behalf by threatening to fire them is also a crime of extortion.
> he can't access anything the Legislature's laws say he can't. Can the legislature make rules for the president without constitutional amendment? I am interested- I’ll see if I can find examples.
It would mean a President is is legally permitted to ignore laws against raping a child on the sidewalk outside 1600 Pennsylvania avenue Ave then murdering all of Congress by blowing up the Capitol.
Recently, a majority on the Supreme Court has claimed there's immunity for "Official Acts", but hasn't laid out any rule for when an official-looking act is actually an unofficial one... They're basically reserving the right to decide later. (Ex: Officially ordering the US military to kill Congress and Supreme Court Justices.)
Not that I want to give the current one any more evil ideas.
Re: DOGE worker’s code supports NLRB whistleblower
#465The fact that they left these packages public on GitHub.. guys you do know you can make things private right? Just shows how dumb these people are honestly
What? They reused public packages that have been public for years. One guy made a public fork with some changes. Is that not what open source is intended for?
Re: DOGE worker’s code supports NLRB whistleblower
#466Re: DOGE worker’s code supports NLRB whistleblower
#467Earlier quoted context omitted.
The repository has been deleted. In addition, 26 other repos have been removed from the account. This is in line with DOGE members' quick response scrubbing data whenever put into spotlight, as previously seen with another "teen hacker". [0] Archived repo page: https://archive.ph/LI7tt ; archived previous repo count: https://archive.ph/tgkg5 0. https://arstechnica.com/tech-policy/2025/04/i-no-longer-hack...
[flagged]
But we know it isn't speculative based on these public data. You're arguing they should have covered up better. I agree. But that doesn't make (a) it okay or (b) this article speculative.
Re: DOGE worker’s code supports NLRB whistleblower
#468> Berulis said he went public after higher-ups at the agency told him not to report the matter to the US-CERT, as they’d previously agreed. If the allegation is true, what would be the motivation of the higher-ups to keep this secret from US-CERT? It appears to be a severe compromise, and the context suggests that much of the rest of the federal government is imminently vulnerable to the same tactics by the same thre…
Re: DOGE worker’s code supports NLRB whistleblower
#469this part of the whistleblower complaint seem way worse: " On or about March 11, 2025, NxGen metrics indicated abnormal usage at points the prior week. I saw way above baseline response times, and resource utilization showed increased network output above anywhere it had been historically – as far back as I could look. I noted that this lined up closely with the data out event. I also notice increased logins blocked…
Any guesses for best possible interpretion? The Russians have infiltrated their PCs with keyloggers and DOGE are working from insecure open networks. The worst possible interpretation is straightforward - they are working for the Russians as agents and let the Russians in or installed the keyloggers for Russia.
They were accessing Github over the internet from superuser accounts they were presumably also using as their user account. Given the code quality, I doubt their opsec is put together, either.
Re: DOGE worker’s code supports NLRB whistleblower
#470Earlier quoted context omitted.
I would have thought that a Russian state sponsored attack would trivially mask the IP to originate from within the USA. This is just brazen.
Sometimes getting caught isn’t a bad thing. If you are trying to seed division between to groups, acting in a way that divides them - e.g., getting caught helping one side - is more effective than what you gain by not getting caught. I struggle to see what Russia would gain with nlrb data, but getting caught “helping doge” furthers distrust between the two sides of our country - which is something they gain from
A list of whistleblowers at American companies who presumably don't want said companies to know the details of their work.