Tbh Ive had some joy using K8Gpt and I’m kind of excited to try Liz for my Rancher stuff.
To me though, RAG AI is good as a semantic search at the moment but you really should check with your own eyes and not assume the convincing string machine has any actual understanding about what it is saying.
Does help though when your eyes are bleeding and your troubleshooting something youre just not sure where to look.
The funny thing from what I’ve read the got the alot of raw audio files too so the people torrent probably are getting higher quality versions then what Spotify transcodes too
Supreme Court outlaws clothes. What criminal acts are hiding in those robs? Only the guilty would hide it
I don’t like that this was removed, but it is very ironic for a AI summary about AI hype fueling a RAM shortage. It was at least properaly labeled and attributes and an open source model.
So Mojo and Python then?
To be fair. SELINUX always seems like THE answer with flexibility it provides with App armor being just SELINUX light…
It would make more sense to me to have better support for leveraging SELINUX primatives to accomplish the same things. I at least, don’t know of any LSM features that can’t be covered user:role:type:security level:catagorey and namespaces?
The issue is always that info is hard to know sometimes and programers can barely stop ourselves from running as root with all files in 777 mode let alone conceptualize those other attributes for files and services
Right. There is probably a certain point where other hardware support is just a happy accident or miniscule effort. Its just there yet for them though it is getting close!
Why should they do it again?
They are basically the exclusive target for GrapheneOS for their feature set:
Non-exhaustive list of requirements for future devices, which are standards met or exceeded by current Pixel devices:
Support for using alternate operating systems including full hardware security functionality
Complete monthly Android Security Bulletin patches without any regular delays longer than a week for device support code (firmware, drivers and HALs)
At least 5 years of updates from launch for device support code with phones (Pixels now have 7) and 7 years with tablets
Device support code updated to new monthly, quarterly and yearly releases of AOSP within several months to provide new security improvements (Pixels receive these in the month they're released)
Linux 6.1, 6.6 or 6.12 Generic Kernel Image (GKI) support
Hardware accelerated virtualization usable by GrapheneOS (ideally pKVM to match Pixels but another usable implementation may be acceptable)
Hardware memory tagging (ARM MTE or equivalent)
Hardware-based coarse grained Control Flow Integrity (CFI) for baseline coverage where type-based CFI isn't used or can't be deployed (BTI/PAC, CET IBT or equivalent)
PXN, SMEP or equivalent
PAN, SMAP or equivalent
Isolated radios (cellular, Wi-Fi, Bluetooth, NFC, etc.), GPU, SSD, media encode / decode, image processor and other components
Support for A/B updates of both the firmware and OS images with automatic rollback if the initial boot fails one or more times
Verified boot with rollback protection for firmware
Verified boot with rollback protection for the OS (Android Verified Boot)
Verified boot key fingerprint for yellow boot state displayed with a secure hash (non-truncated SHA-256 or better)
StrongBox keystore provided by secure element
Hardware key attestation support for the StrongBox keystore
Attest key support for hardware key attestation to provide pinning support
Weaver disk encryption key derivation throttling provided by secure element
Insider attack resistance for updates to the secure element (Owner user authentication required before updates are accepted)
Inline disk encryption acceleration with wrapped key support
64-bit-only device support code
Wi-Fi anonymity support including MAC address randomization, probe sequence number randomization and no other leaked identifiers
Support for disabling USB data and also USB as a whole at a hardware level in the USB controller
Reset attack mitigation for firmware-based boot modes such as fastboot mode zeroing memory left over from the OS and delaying opening up attack surface such as USB functionality until that's completed
Debugging features such as JTAG or serial debugging must be inaccessible while the device is locked
The rapid growth model only makes sense for people looking for investors and the promise to snag a customer base once their hooked.
Value has a lot to lose but mostly margins to gain.
Listen I’m for keeping them pushing towards ethical contributions to the ecosystem, but I also entirely understand them not doing so just for charities sake alone.
Fair on the release part lol. I didn’t know that, but I guess the ignore part is still an issue since people want them to get it to work with other hardware out of scope, or worse Nvidia
Project scope. It makes more sense for them to make a distro that solves currently unsolved spaces directly related to their market (merging PC with handhelds, consoles, and VR). More scope either means more hours or more spread of the existing hours accros the added work.
They have been contributing alot back to upstream which does help Linux gaming in general alot.
You want them to release SteamOS and ignore all user feedback except for Steam hardware some how? Otherwise that’s all cost. Or significant brand risk.
Tbh I’m not sure what the conversion rate to sales actually would be. The numbers of sold games on the steam machine vs the average machines rates will be a better indicator of that IMHO. The Steamdeck is biased in that showing the form factor support is also an important point for games on the deck.
I would rather them keep investing in the ecosystem then try to rush for growth and have to enshitify to keep it.
Largely people pay for games regardless. From Steams perspective investing the store profits into Linux gaming is a market risk reducer and a cost center for producing viable hardware platforms.
Its not a revenue stream at the moment. If a million more people started running it tommorow on non-steam hardware and didn’t adjust the game buying habits, it would be a net loss for Value, as their support costs would rise with no increase in revenue.
The best case for them is that it acts as a conduit for good PR, and user generated content for the platform (i.e. mods, apps, and of course FOSS merge requests).
Sweet! Great place showing off the projects and companies that are truely working towards respects your freedom type of computing!
I would add Oxide to the server list they are definitely in this space
Not the IP but hope this git link helps: https://gitlab.com/here_forawhile/nanogram.git
Tar ball link if that is better for you: https://gitlab.com/here_forawhile/nanogram/-/archive/main/nanogram-main.tar.gz?ref_type=heads
Was macos at work, now Linux dev machine. Its a big up.
To be honest, all those are web apps now shrug. Zoom, slack, teams, docs, sheets, <insert word named app here>, all open in the browser. So IDC what the OS is for them. Linux Zero-Touch deployments are still in progress IMHO so I get why they arent here yet for a lot offices, but we are closer now than ever (thanks atomic OSs!).
Bazzite and Kinote though I use distrobox and k8s alot for messing with other distros/apps. Vscodium and neovim. Vscodium is loaded up with nearly anything IaC or kubernetes related and Continue for some AI stuff (pointed to local and mistrial). Also heavy opinionated stuff for Python like black, etc (I want my ide to yell at me to make better code). Some GitHub and git lab add-ons too. Nvim is just as is.
Definitely overkill lol. But I like it. Haven’t found a more complete solutions that doesn’t feel like a comp sci dissertation yet.
The goal is pretty simple. Make as much as possible, helm values, k8s manifests, tofu, ansible, cloud init as possible and in that order of preference because as you go up the stack you get more state management for “free”. Stick that in git and test and deploy from that source as much as possible. Everything else is just about getting to there as fast as possible, and keeping the 3-2-1 rule alive and well for it all (3 backups, 2 different media, 1 off-site).
I wonder what the best conversion rate from uranium kcals to human consumable cals would be.
Like is nuclear power to LEDs to plants the best route? Maybe radiation to fungus to some kind of slurry?