So again, because we make backups before letting AI touch anything:
“Hey slop machine, you fucked up. Restore the last backup and document the mistake you made in AGENTS.md so we avoid making that mistake again. Im going to go make a coffee, brb”
So again, because we make backups before letting AI touch anything:
“Hey slop machine, you fucked up. Restore the last backup and document the mistake you made in AGENTS.md so we avoid making that mistake again. Im going to go make a coffee, brb”
Oops, slop machine broke something.
“Hey slop machine, you fucked up. Restore the last backup and document the mistake you made in AGENTS.md so we avoid making that mistake again. Im going to go make a coffee, brb”
Hardware I’m running:
I’m mainly using these MoE models:
Qwen-3.6-35B-A3B
Gemma4-26B-A4B
I created git repos on my main workstation for each homelab server/service I maintain that keeps:
I just point a local LLM (offline model that runs on my workststion) into those repos and ask it to perform certain things on those servers. It can do things like update packages, install packages, make config changes, set/check permissions, read logs (and fix errors in real time), and check the health of the overall system.
I have it run pre backups before making changes, then post backups once its done.
Once changes are in place and everything is running okay, I ask it to update documentation in the repo and tag the release.
I use opencode that connects to a llama.cpp service. opencode lets me gate the AI so that any elevated commands that it needs to run (e.g. sudo or ssh), I have to approve it. It cant just go around making changes without permission.


This question is how new apps are born


They should probably jail the CEO for this like they would any other “hacker”


This will probably be the actual name tbh


EdgeOS!
Also, itll still prompt you to make EdgeOS your default OS


They gotta be trolling the entire linux userbase at this point.


Those devices should most certainly be on two separate networks. Internet facing devices should be on a DMZ and not be allowed to talk to your internal network. You can then allow your internal network reach your DMZ devices, but only allow return traffic from the DMZ.


So greasy its nickname is now Burger


Poor storage drives adding on power cycles


Check out Luanti
Dont get me wrong, its nowhere near as polished, but ive had a blast with it while playing with family and friends.
One thing you could deploy throughout all your internal networks are honeypots that send alerts upon ANY network activity. Nobody should be hitting those at all.


Microsoft is literally requiring its devs to use AI to write parts of Windows
Uh oh, looks like you didn’t read far enough:
So again… Well, do I need to paste it again?