The right way to do this is to hire a group of developers and have test volunteers report workflow problems - then FIX them - then iterate. That's the point of choosing an open source solution.
Eventually there would be no problems remaining.
But so many possible scenarios exist that it's impossible to guess what happened here.
PS _NSA_KEY
There are apparently other unpatched vulnerabilities that are known but 'too busy':
It sounds like this fix got done because it was 'accidentally' posted as a public PR.
Yeah, the threat actor would need a foothold on the PXE network, which is a private VLAN (or better) in the competent case.
That's why we worry about APT's and such.
Granted, you'll find people on certain cloud providers who do far too much on a public IP.
Think back to 2+ years ago. January 2024. What sort of government did we have? What Administration was in office?
From the Wikipedia:
" and the Bureau of Land Management extended the auction to January 25, 2024 to allow for increased bids.[14] In 2024 the remaining reserve was sold to the highest bidder, Messer Group.[15] "
And, perhaps, you begin the effort by 0) migrating the documents, all of them, even archival docs, to earlier and earlier versions - reducing dependency on features perhaps not supported in your POA platform, and 1) testing against the POA and refining.
Drop-in replacements for Office do not exist. Nothing out there. So downgrade and find a POD that can be supported.\
Seems pretty basic, just costs in the preparation.
Not that SCOTUS (nor any high court in the EU or other countries) has concluded this determination, but so far the general claim is that AI-generated content (images, movies, writing), while it may (or rather, does) contain copyright violations for stealing from others, it itself can't be copyright protected because no human was involved in making the final product. It is automatically public domain.
So that leaves the question - at what point does a vibe-code project be considered public domain and thus not protected by a license?
Straczynski shared his experiences working with Koenig on his FB page. A good read.
What if someone has fifty windows open with fifty tabs each?
Asking for a friend.
Solid effort - good job.
It's a bummer if any of the employees got rug-pulled but many of the best employees will strike out on their own, form new companies with working conditions they value, and likely hasten Skydance's demise.
"they have been more then forward with their intent to replace us all with AI and robots"
Citations needed. Focus on the word 'all'.
I get the anger towards technology displacing human workers with no apparent plan to re-employ them elsewhere. But this is just the latest in a series of such revolutions. AI isn't replacing plumbers any time soon. Unless the AI can direct robots to manufacture housing with preassembling utilities, but that's a fantasy away from happening.
I was repairing desktop calculators for a while until they became too cheap to bother. I repaired typewriters and older, more proprietary word processing systems, until PCs took over. Then I went into the PC service and support business. And the PC networking business, because networking was a thing. Then an ISP, because the Internet was seriously sucking the air out of the world. Then I migrated into support and customer service, which after 17 years became much less demanding of head count, and now I've retired, 50 years after those nixie tube calculators sat before me and my soldering iron. There is more after this particular bubble. Watch. The real threats are philosophical, disguising as politics and religion, of which they are neither. Ideas spur more killing, because it is in the end all ideas.
And dont pay anywhere close to what they were making.
nah, a RS code can correct a tiny bit of loss but two metadata copies can correct a bad sector or even track if you're lucky.
Different requirement spaces.
The idea this guy has might make embedded devices slightly more long-lasting.
They usually have quantity one of a cheap storage part and a bad block in the wrong place could brick the whole thing.
It would only be useful in the case where maybe the build is 12MB and the chip is 16.
Most vendors won't ever pay extra for this.
I suspect the people who hate it don't have problems it solves.
Maybe a very basic home laptop is fine with SysV today and they don't want to learn anything new.
Personally I've been able to retire thousands of lines of scripts I'd written to handle complex things with many edge cases and ugly devops modules that are no longer needed with more recent releases.
There's just no userland interface to many of the events it can respond to and it's not easy to write a new C++ daemon to handle each need that comes up.
At this point it's largely a functional API to kernel events in the way I use it. That's the DOTADIW perspective for me. I still have services call my scripts where it doesn't handle what I need. It would be crazy to ever expect it to handle everything.
But just because I need to handle complex things at scale sometimes doesn't mean everybody else does. If I want to run debian with X11 and emacs and you want to run Devuan with Wayland and vi, you'll get no argument from me.
Who has time for drama these days?
No amount of genius can overcome a preoccupation with detail.
