by shinryuu on 2/4/25, 3:05 PM with 654 comments
by taylodl on 2/4/25, 3:09 PM
by malfist on 2/4/25, 3:14 PM
Elected or unelected, politicians with an agenda should not be in charge here.
by resters on 2/4/25, 3:23 PM
I used to respect Elon for risking a lot of his own capital on new ventures. But now he's turned into a socially conservative internet troll.
by HumblyTossed on 2/4/25, 9:06 PM
by erentz on 2/4/25, 6:44 PM
by spacemanspiff01 on 2/4/25, 10:44 PM
It sounds like, from the reporting, one person is modifying a large complex system that handles trillions of dollars and pushing directly to production.
Also he is not familiar with the system, having first encountered it a week ago.
Also the people who do normally have access to this system do not know what he is exactly doing, because normally, it is illegal for them to even access the system in the same way.
by belter on 2/4/25, 5:17 PM
- Tax Return Info: Name, SSN, address, income, deductions, payments/refunds.
- Enforcement Records: Audit trails, payment plans, liens/levies.
- Federal payments (e.g., tax refunds, Social Security), direct deposit info, delinquent debt details.
- Accounts for U.S. Treasury securities (personal data, account activity).
- Sanctions Enforcement: Basic identifiers (name, address), transaction details for compliance checks.
- Financial Crime Data: Suspicious Activity Reports (SARs), Currency Transaction Reports (CTRs), limited personal/transaction info tied to money laundering or terrorist financing investigations.
- Investigative files related to Treasury programs (potentially includes personal data).
by yalogin on 2/4/25, 8:48 PM
by flaminHotSpeedo on 2/4/25, 3:39 PM
How can this department turn around and do this and still maintain they're doing the right thing? By their own admission they know this a bad idea
by polotics on 2/4/25, 4:52 PM
by samsk on 2/4/25, 10:11 PM
by macawfish on 2/4/25, 5:07 PM
by mikewarot on 2/5/25, 1:20 AM
Elon doesn't have a strong track record of getting things right the first time.
by bbor on 2/4/25, 3:14 PM
by skepticATX on 2/4/25, 3:13 PM
by 01HNNWZ0MV43FF on 2/4/25, 3:21 PM
by hamburga on 2/4/25, 4:37 PM
by LorenDB on 2/4/25, 3:16 PM
by 1970-01-01 on 2/4/25, 9:54 PM
...
>All that is known is that Marko can “access and query” SPS and that there was someone who gave Marko a “tour” of the facilities. We do not know where they are in operationalizing any control. One senior IT source can see Mark retrieving “close to a thousand rows of data” but they can’t see the content because the system is “top secret” even to them. No source I have has knowledge of what DOGE is doing with the data they are retrieving.
So the (d)evil remains hidden in every one of their details! What does 'write code' actually mean? A DB query? What exactly are these 'most sensitive' systems in the US government? A COBOL DB??
Compare the backups.
You DO have them off-site?
by TrackerFF on 2/5/25, 9:38 AM
The strategy here is:
1) Trump issues some unconstitutional EO to abolish a federal department
2) Musk and DOGE go to work
3) Some federal judge blocks the EO
4) Some acting lackey of Trump ignores the court order. DOGE continues to dismantle the department from within
5) Even if the judge orders an arrests, no-one will enforce it
6) Congress does nothing
By the time anyone actually gets held accountable, the departments will have been pillaged and dismantled. DOJ and the AG will not go after anyone involved, Trump orders pre-emptive pardons for all involved in federal crimes.
by bbqfog on 2/4/25, 3:16 PM
by liontwist on 2/4/25, 10:27 PM
by cratermoon on 2/4/25, 4:15 PM
by code_for_monkey on 2/4/25, 3:28 PM
who tf downvoted this show yourself groyper
by unyttigfjelltol on 2/4/25, 9:09 PM
Why isn't the very existence of this box the problem?
by astroid on 2/5/25, 1:15 AM
These articles are all so circular I have resorted to asking CoPilot to analyze them and tell me what each source is, if they are 1st 2nd or 3rd party, and whether or not they are anonymous.
In this article, the analysis came out with:
Let's break down the claims and sources in this article:
Crises Notes: Reports that the Trump-Musk Treasury payments crisis of 2025 involves the Department of Government Efficiency (DOGE) gaining access to the Treasury Department's payment system. The article mentions concerns about the potential for irreversible damage to the systems and the exposure of sensitive personal and financial information1. The sources are unnamed, and there is no direct evidence provided.
CBS News: Reports that DOGE has access to the Bureau of the Fiscal Service, which disburses trillions in payments each year, including Social Security checks and federal salaries. The article mentions concerns from consumer advocates and Democratic lawmakers about the potential risks of this access2. The sources are unnamed, and there is no direct evidence provided.
Truthout: Reports that labor unions and an advocacy group have sued the U.S. Treasury Department to halt DOGE's access to the critical government payment system. The article mentions concerns about the scale of the intrusion into individuals' privacy and the potential for unauthorized access to sensitive information3. The sources are unnamed, and there is no direct evidence provided.
In summary, all the sources cited in the article are anonymous, and there are no first-party sources or direct evidence provided. This makes it difficult to verify the claims independently. The lack of named sources and concrete evidence raises questions about the credibility of the claims.
Also, I will go ahead and paste my previous output from the other articles below (I'm going to post them as child comments so this isn't just a huge wall of text):
by archagon on 2/4/25, 4:11 PM
> Josh, are you a little crestfallen they beat you to it? Well, sure but this is a business is an ocean of ‘arrgghhs’ and honestly the information being out is the big thing. Here are the additional details.
> I’m told that Elez and possibly other DOGE operatives received full admin level access on Friday January 31st. The claim of ‘read only’ access was either false from the start or later fell through. The DOGE team, which appears to be mainly or only Elez for the purposes of this project, has already made extensive changes to the code base for the payment system. They have not locked out the existing programmer/engineering staff but have rather leaned on them for assistance which they appear to have painedly provided hoping to prevent as much damage as possible – ‘damage’ in the sense not of preventing the intended changes but avoiding crashes or a system-wide breakdown caused by rapidly pushing new code into production with a limited knowledge of the system and its dependencies across the federal government.
> Phrases like “freaking out” are, not surprisingly, used to describe the reaction of the engineers who were responsible for maintaining the code base until a week ago. The changes that have been made all seem to relate to creating new paths to block payments and possibly leave less visibility into what has been blocked. I want to emphasize that the described changed are not being tested in a dev environment (i.e., not live) but have already been pushed into production. This is code that appears to be mainly the work of Elez who was first introduced to the system probably roughly a week ago and certainly not before the second Trump inauguration. The most recent information I have is that no payments have as yet been blocked and that the incumbent engineering team was able to convince Marko to push the code live to impact only a subset of the universe of payments the system controls. I have also heard no specific information about this access being used to drill down into the private financial or proprietary information of payment recipients, though it appears that the incumbent staff has only limited visibility into what Elez is doing with the access. They have however looked into extensively into the categories and identity of payees to see how certain payments can be blocked.
by mandeepj on 2/4/25, 6:23 PM
by treebeard901 on 2/5/25, 5:19 AM
...DogeCoin??
by gammarator on 2/4/25, 3:16 PM