As a former RedHat advocate it sucks honestly, I have to find companies like Rancher and Suse that off truly FOSS products now. Like I want opensource devs to get paid if they are being depended on, but the RedHat paywall makes avoiding the vendor lock or trying to be cost flexible a legal land mine. They also offer more and more proprietary rebrands of FOSS projects that I fear will get EEEd as well.
Hey, at least remote works been really putting nails in the coffin of printed documents floating around.
But seriously keeping to a good set of tools, providing them at scale and some training will hopefully make the fall back to spreadsheets less attractive to at least the middle wave of adopters.
Couldn't the fact that AI generated content be reproduceable if give the exact parameters(or coordinates in latent space) and model help remove the confusion? Include those as meta data and train investigators on how to use to distinguish generated content from actual evidence.
Providing information for your care providers to act on it. At least that's why I would WANT to have it. Is it being effectivly used like that though? I have no idea.
Right. Paid Gitlabs features tend to be targeted as an all in one DevOps platform for larger scale organizations. So how do you do support tickets, CI/CD, feature tracking and coordination for a portfolio of products, documentation, revision control, code reviews, security reviews, etc? In Gitlabs world the answer is Gitlab, with integrations with other enterprise software. It's HUGE. That said I've never heard of an organization (probably due to ignorance not lack of existence) actually doing all of that.
I personally I'm kind of leaning towards building a proof of concept of forgejo, tekton, and maybe Odoo to see if it can cover what my org is actually doing, but he'll we pay for tons of stuff but the amount of excell sheets floating around doing this is wild...
Being FOSS doesn't it make secure, but it doesn't make it more possible for people to actually test and secure it (people with less interests in it being seen as secure, but instead actually secure).
It's a harder con to build a real looking fake safe, hoping no one will actually test it out, then just lying about what's behind a curtain no one is allowed to look behind.
This risk extends even more to non-foss software though as organic fixes can't happen and the company that owns it HAS to fix it for you. Not all purchase agreements say they have to do this, and again it is our organizations that bare the risk then.
To be honest I'm a FOSS advocate, but when I recommend software I absolutely mention that getting devs (capable of fixing that software) in a SLA for critical bugs is what the absolutely should do, or accept the security risk or operational risk of insecure software.
That because being perfectly anonymous against all of the most advanced actors is near impossible that it's not worth it. Every step taken DOES help reduce the amount of info out there on you and the amount of parties that have access to it. Not only that every step you take helps those around you too.
The title "Makes EL source available" made me very frustrated for a second lol
This is good news, I am glad they have officially released FOSS code for EL and not, which I thought I read, them moving from a FOSS license to a source available license.
I really wish I had a proper portal interface that put a cli tools in my path and asked me if I'm sure I want to give the tool permission to that path (you know because of filesystem separation, obviously don't ask if it's already given that permission).
Basically I agree, flatpaks shell interactions are sub par.
Synergy that!