DOGE worker’s code supports NLRB whistleblower
111–120 of 586 posts
Re: DOGE worker’s code supports NLRB whistleblower
#112[flagged]
Re: DOGE worker’s code supports NLRB whistleblower
#113Re: DOGE worker’s code supports NLRB whistleblower
#114> Ge0rg3’s code is “open source,” in that anyone can copy it and reuse it non-commercially. As it happens, there is a newer version of this project that was derived or “forked” from Ge0rg3’s code — called “async-ip-rotator” — and it was committed to GitHub in January 2025 by DOGE captain Marko Elez. Original code: https://github.com/Ge0rg3/requests-ip-rotator Forked: https://github.com/markoelez/async-ip-rotator Code…
Re: DOGE worker’s code supports NLRB whistleblower
#115I find the following bizarre. Ignoring who this marko guy is, why would a random person post such a "take down" of the repo? I have never randomly passed by a repo and wanted to just dunk on it. Also this critique reeks of being AI generated. > On February 6, someone posted a lengthy and detailed critique of Elez’s code on the GitHub “issues” page for async-ip-rotator, calling it “insecure, unscalable and a fundament…
Re: DOGE worker’s code supports NLRB whistleblower
#116Earlier quoted context omitted.
I fully believe there's a stack of pardons in Trump's drawer for everyone involved in this debacle. I can't imagine breaking so many laws all over the government if you thought you'd ever have to face consequences. The alternative to pardons in preventing the next congress & administration from cleaning this up is too dire to really contemplate.
Time to remove the pardon powder. Has it achieved anything productive in the last 100 years?
Re: DOGE worker’s code supports NLRB whistleblower
#117I find the following bizarre. Ignoring who this marko guy is, why would a random person post such a "take down" of the repo? I have never randomly passed by a repo and wanted to just dunk on it. Also this critique reeks of being AI generated. > On February 6, someone posted a lengthy and detailed critique of Elez’s code on the GitHub “issues” page for async-ip-rotator, calling it “insecure, unscalable and a fundament…
Why wonder? The user who wrote it seems to be a pretty well established user, and their public repositories suggest that they work in adjacent contexts, so it's entirely plausible they attempted to use async-ip-rotator in one of their projects.
The public repos for this person that I could find that weren't forks with no activity to upstream consisted of a dice-rolling guessing game, rock-paper-scissors, and some kind of framework for downloading and transcribing audio files that does not yet download or transcribe, but implements a whole bunch of boilerplate. I find it rather difficult to believe this person engaged in a good-faith review of the async-ip-rotator code base.
Re: DOGE worker’s code supports NLRB whistleblower
#118Earlier quoted context omitted.
A twisted justification for suggesting someone who broke serious laws not face consequences. We live in a nation of laws, whether or not conspiracy-minded individuals prefer to follow them.
> We live in a nation of laws You stopped living in a nation of laws a while ago. Now you live in a nation of might makes right.
Re: DOGE worker’s code supports NLRB whistleblower
#119[flagged]
[flagged]
> The employees grew concerned that the NLRB's confidential data could be exposed, particularly after they started detecting suspicious log-in attempts from an IP address in Russia, according to the disclosure.
Re: DOGE worker’s code supports NLRB whistleblower
#120Someone needs to go to prison over this. It’s not just a misunderstanding, it is an intentional attack on every US citizen.
You’d have to prove a crime here to send someone to jail, correct? What would the charges be?