Companies have until January 1, 2026, to create memory safety roadmaps.

Not really the same as dropping entirely

Underrated meme

I was going to say this too, but I’ve never cross compiled a cmake project so I wasn’t sure how much overhead there would be

You can compile on a big pi and copy the binary to your zeros. No need to compile on a zero lol

Fedora Linux and expectations for part time remembering it is not send to the same room as the other one that is pertinent

I just did the same thing with llama and got the same thing

Reminds me of this Steve Huges joke

Youtube

I use privatebin. Has some good features but I dont think it has login

So it’s windows emulating linux emulating android emulating linux?

I’m interested to hear how that works out for you

You can set up multiple remotes for a repo and push to a local git server and github at the same time

Try running docker logs for the tailscale container to see if it gives any more info

I had never heard of radxa. Looks awesome!

Have you tried taking the metwork config out of the compose file and just letting podman handle it?

Anybody else notice the first graph goes from 2020 to 1996?

Just to offer the other perspective. I started with podman years ago. I knew very little about containers and I would say it made the learbing curve a lot steeper. Most guides and README’s use docker and when things didnt work I had to figure out if it was networking, selinux, rootless, not having the docker daemon, etc… without understanding fully what those things were because I didn’t know docker. But when I started running stuff on kubernetes, it was really easy. Pods in podman are isomorphic to kubernetes pods. I think the pain was worth it, but it was definitely not easy at the time. Documentation, guides, and networking have improved since then, so it may not be as big of a deal now

Quadlets with podman have completely replaced compose files for me. I use the kuberentes configs. Then I run a tailscale container in the pod and BAM, all of my computers can access that service without have to expose any ports.

Then I have an ansible playbook to log in to the host and start a detached tmux session so my user systemd services keep running. Its all rootless, and just so dang easy.

For every sever install I’ve had, flatpak defaults to the system install which requires a password. You have to explicity pass the --user flag.

I’m not sure how to make it the default