471–480 of 586 posts
Earlier quoted context omitted.
The best outcome for them and other potential powerful forces is an America so roiled by internal conflict that it can’t now or ever do anything. Yeah Trump winning seems to help them in Ukraine but their need is disruption as much as different policy in the longer term.
While I'm just guessing I'd think it would be better to wait until Ukraine is done and trump is out of office. Creating mistrust in Doge only helps Democrats
Earlier quoted context omitted.
I guess I should have been clearer - the "private repository" mentioned in that bill only has to be available for government employees, and even then only on request. Public repositories are an option, but the government doesn't have to choose that option. The main point is to encourage reuse within the government, not to be a source of free public domain software for the public.
Almost everything the government makes IS public domain, including the software. https://en.wikipedia.org/wiki/Copyright_status_of_works_by_t...
Earlier quoted context omitted.
That's straight up traitorous. DOGE needs to be shutdown and everyone of them held as a flight risk while the whole thing is investigated.
They work for Trump so they'll never be held to account, even if a Democrat wins the next election (assuming even have one and it's fair and free) I never thought I'd be calling for UN observers for an election in the US but here we are
Why? If Democrats take the House in the midterms, which looks more likely the longer Navarro and Musk have West Wing access, they can basically turn these folks' lives into a living hell of back-to-back hearings (and contempt charges down the road). And if Democrats win the next election, they'll presumably put someone with a pulse in charge who doesn't take two years to bring the most important cases of their administration to the docket.
I 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…
the 2nd comment in the issue explains why the 1st was posted pretty clearly
Hello, I work in incident response and cyber forensics within the private sector and as a government contractor. I'm familiar with the government contracting company that currently holds the SOCaaS contract with the NLRB - it's MindPoint Group. They share the a SOC with the DOJ. I reviewed the whistleblower’s evidence, and I have significant doubts about his claims. Firstly, anyone claiming that "the whole government…
Earlier quoted context omitted.
The "when requested" is the point I was making. FOIA is how you request such software. If you want a copy of the elisp libraries I wrote to automate creation of field devices on military fuel farm SCADA systems, you'll have to submit an FOIA request. Unless someone at the DoD decides to share it out of the goodness of their hearts, you have to ask for it.
Sounds fascinating! Other than the FOIA bit. Do you have a blog post or something with more detail about this work?
My engineer gives me a list of (for example) valve actuators on a site. I open that list in Emacs, manipulate it a bit, and then use it as input to a function I've written. That function generates a CSV file with things like tag name, Modbus ID, polling method, etc. that I can import into Wonderware. It's considerably faster and less error prone than manually creating and configuring hundreds of instances.
I say it's not interesting because most people in my position write little bits of code like this to automate the repetitive parts of our jobs. I just do it with elisp instead of Excel or Python.
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 relatively confident this critique is AI-powered. The dead giveaways: 1. Verbosity. Developers are busy people and security researcher devs are busy even moreso. Someone so skilled wouldn't spend more than 2-3 sentences of time in critiquing this repo. 2. Hostility. Writing bug free code is hard, even impossible for most. Unless your name is Linus Torvalds, Richard Hipp, or maybe Dan Abramov, most devs are not co…
Verbose hostility of that kind and throwing stones, even nitpicking with exaggerated outrage are no exception. And lack of experience never stopped people from feeling and behaving like god given gift to programming profession.
this 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…
Probably the least expected location to connect from, if it was genuine. Not saying it necessarily isn't, but it's not usual either and doesn't make much sense.
this 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…
I wonder why the "no-out-of-country logins" block happens after verifying login credentials and not before, which would make more sense to me.
This context enables two important things:
- Granular exceptions: If Alice is attending a conference in Toronto, you can say "Allow Alice to log in from Canada next week" without opening Canada-wide logins for everyone. Pre-auth geo-blocking forces you into an all-or-nothing stance.
- Better threat intelligence: A valid login from an unexpected region (e.g. Moscow when Alice is normally in D.C.) is a far stronger signal of compromise than a failed attempt. Capturing "successful login + wrong location" helps you prioritize real threats. If you block pre-auth, you'd never know Alice's account was compromised.
Putting geo-checks after authentication gives you precise control over whom, exactly, is logging in from where, and offers richer data for your security monitoring.