Is anyone else actually finding it harder and harder to read LLM generated text? I find it quite tiring, my brain just does not want to get through it.
28,711 karma · joined March 14, 2012
Is anyone else actually finding it harder and harder to read LLM generated text? I find it quite tiring, my brain just does not want to get through it.
I don't know why they didn't decide to do that, I guess they just make poor decisions to be cheap. Otherwise it's a complete mystery.
They probably have 1-2 IT staff, who have been paid significantly under market value compared to private sector.
Management was not management of an IT organization, and probably did not really understand the trade-offs or what they'd lose by not spending more money on IT. Their IT staff was probably super busy and over-worked and also (not to throw them under the bus) not experienced enough to really advise them, and if they had and had tried to advise them, would management have decided that doing less programmatic work to pay for it, and having IT people at least temporarily spend less time on whatever they do to support regular business, to set up and support backups, was worth it? Maybe, maybe not. Again, the managers probably have little experience with IT. The whole organization is probably well under 100 people.
Source: I work in non-profits.
Why is HN always focused on suggesting there's a person who could have easily made the right choice if they weren't an idiot?
Only if you haven't been reading HN very long!
Is it possible to ever read a piece by LLMs that isn't written by LLMs?
It sounds like you guys think OP was mistaken, whatever analysis NIST was doing that they reduced in 2024 would not have prevented this anyway?
Legit question, I'm trying to understand!
OP says:
> Hit by a massive surge in vulnerability reports, NIST effectively hit pause on deep analysis. CISA and other Authorized Data Publishers (ADPs) tried to step in with their own enrichment efforts, but the global pipeline is now fragmented and drowning in a massive backlog. Because no step in today's system actually requires a proof-of-concept or bug reproduction, a plausible-sounding fake advisory can slide right through the pipeline and end up in GHSA, downstream databases, and enterprise scanners.
Do i correctly understand you are saying you think they've mistunderstood the diagnosis of what changed, the 2024 change to NIST didn't actually make it any more likely for a fake advisory to go through pipeline?
To be sure, the suggestion is not funding cuts, but an increase in workload with same funding.
Here is the 2024 NIST announcement OP links to: https://nvd.nist.gov/general/news/nvd-program-transition-ann...
> Currently, we are prioritizing analysis of the most significant vulnerabilities. In addition, we are working with our agency partners to bring on more support for analyzing vulnerabilities and have reassigned additional NIST staff to this task as well.
The OP described this as "NIST effectively hit pause on deep analysis. "
It does sound like they stopped doing something they used to do in 2024. I personally have definitely not spent a lot of time directly interfaced with NIST on cybersecurity in decades past, I know nothing about it, just what I read in OP.
Are you saying the OP was wrong to call what NIST used to do "deep analysis", and/or that the thing NIST stopped doing was "purely ministerial/clerical" in a way that it would not have caught fake reports anyway, contradicting the OP? Or other?
Again, to be sure, the OP's suggestion was not that this was caused by NIST funding cuts, but by "a massive surge in vulnerability reports,"
(Obviously the answer is not, we only care about funding offensive capabiltiies).
It does seem interesting, and possibly welcome if there were a configuration option or even a way to set individual notifies as serialized or not.
Violins are basically ancient and evolved gradually over huge time spans, yes.
But saxophones -- invented by a guy named Adolph Sax and patented in France in 1846! It really was a kind of new thing, combining aspects of brass and woodwind instruments in ways that hadn't been done before. I think it's fair to say he invented it as a new instrument. (What legal protection that should get how is another story, I don't know that I like patents honestly). https://en.wikipedia.org/wiki/Saxophone
Sax was really mad about manufacturers reverse engineering and copying his saxophone without a license and tried suing them etc, for the period before his patent expired, but it was still being copied a lot -- it was a new thing people were excited about. Once the patent expired, it was definitely a free for all.
The observations you are reporting are from images you created yourself and you know are in fact progressive jpegs? (not "regressive", although that's funny). There are of course other techniques to start with a lower resolution image that do "work" (in the sense of actually displaying a lower resolution image first at least).
It was released 2 and a half months before Google IO.
The way I read this, they decided to announce it at Google IO because of the attention the project released by the Developer Relations team got. No one with inside knowledge has said the "official tool" (not from Dev Relations) was already planned when it was released. Maybe it was. Maybe a guy on the Dev Relations team would or should have known it was if it was. Easy for me to believe it was not however.
So, yeah, whatever it is, I'd say it looks normal.
[1] https://github.com/googleworkspace/cli
How do you know that's true? Do you have information the rest of us don't?