Uh oh, looks like you didn’t read far enough:
On Monday, two days after the incident occurred, Mr Crane confirmed that the data had been recovered. The Independent has reached out to Anthropic and Cursor for comment.
So again… Well, do I need to paste it again?
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
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.
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.
Healthy storage pool? Any disk errors?
HDDs or SSDs locally?
The big update is coming soon. They’ve been working on it for a long time now. Its in the final stretch and should hopefully be in TestFlight soon.
Swiftfin is an official tvOS jellyfin app:
https://apps.apple.com/us/app/swiftfin/id1604098728
This is per:
Sorry, wish I was able to share more. I honestly JUST started diving into this stuff after your post. Learning a lot from the various other comments though. Hopefully some of the other commenters can help you get the answers you’re looking for.
Ollama is in the Arch Linux package repository, whereas llama.cpp is in the AUR. Both options are available.
https://wiki.archlinux.org/title/Llama.cpp
Also, looks like Ollama is mostly written in Go and C, versus C and C++.
VC backed or not, both packages are under the MIT license.
https://wiki.archlinux.org/title/Ollama
Ollama is an application which lets you run offline large language models locally.
Solar flares and even the occasional random neutron particle hitting your equipment can cause some weird issues. If its just a one time occurrence and it doesn’t happen again, I wouldn’t worry too much about it.
You could make a document describing what each set of data is, if its useful to anyone but yourself, or if its safe to delete. You could offer suggestions of what to do with each set. I think of it as a treasure map that you leave behind. Maybe they will be interested in it, maybe they will pass it on to someone else.
Depends on the admin.
Arch servers are just fine. Just be sure to pay attention to Arch News to watch for manual interventions on certain updates. If anything, the older Debian packages can cause headaches occasionally. I personally use both distros as servers for different use cases.
1.) Check the jellyfin logs and see what kind of errors youre getting when adding media folders.
2.) check your firewall rules on the jellyfin server, as well as your local router/switch and make sure you’re allowing access to the jellyfin port
Huge! Feels good, huh?