*stealing the designs for

Settings

Well they didn’t do it with Botox.

Your goal isn’t super clear from the post.

Are you asking how to host an OS on an NFS share?

Honestly, 800 stars isn’t a huge impact anymore on its own. I think the age of the repo and frequency of updates matters more. If there is a fork that is more active, people will switch to it.

Some states have open data. Unsure if it’s in Json though.

Also, this answer.

Yeah, so if you’re running rootless containers, they aren’t run by root, and for added security, you don’t want them run by your normal user because if they get broken, then they’d have access to what your user has access to. Just create another user that only runs containers, and doesn’t have access to your things or root.

Wireguard is a VPN, so that’s not going to help you much here unless you’re forwarding all your traffic through a remote server, in which case anyone gets in there will still be able to get your local machines. It’s another hop in the chain, but that’s about it.

If you want to be more on guard about reacting to attacks, or just bad traffic, you probably want something like Crowdsec. You’ll at least be able to detect and ban IPs probing your services. If that’s too much work, leverage OoenWRT reporting and some scripting to ban bad actors that probe your firewall and open ports. That’s a good first step.

If you’re concerned about the containers, consider using something more secure than dockerd. Podman rootless with a dedicated service user is a good start. Then maybe look at something more complex: Kata, gvisor, lxc…etc. The goal being sandboxing the containers more to prevent jailbreaks.

That’s an IPv6 address forwarding to port 3001.

I dunno about that. It’s how I see stuff outside and let light into my house. I’d hate to not have them.

This is the correct answer, but you need a few things to clarify:

1. The issue isn’t the Docker system service. Don’t make that depend on Tailscale
2. Add a healthcheck and restart policy to the container to make it fail when conditions aren’t met, and restart until they are successful
3. Build in some time tolerance at the service level inside the container to prevent it from flailing if your Tailscale healthchecks don’t pass after they initially start. Don’t rely solely on container health checks to ensure it works properly as that might not always be possible.

So many classics in here.

The transfer speed isn’t the big issue, it’s the density and reliability. Packing more heat generating stuff onto the SoC package just makes it more difficult to dissipate. The transfer of data to where it needs to be is still the same, so the trade-off is pretty null in that sense except reduction of overall power consumption.

If it’s win98, you probably want a 32-bit win98 Wine prefix instead of Dosbox.

Call me when they actually show it flying.

deleted by creator

👍

Yes, because each one has been. Just because it’s “Apple” and you think it’s better every iteration is a mistake on your part.

Cool, so the version from many years ago related to OP’s question…how?