for a homelab I don’t think it’s feasible to fully review the source code of everything you install

Here’s what you can actually do:

• Consider if you actually need the application and stop applications you don’t use
• Don’t allow public access unless it is necessary, consider VPN/reverse proxies with client authentication (if supported)
• isolate applications that don’t need to talk to each other
• • see also rootless podman, firewalls, virtual machines, etc
• • don’t forget network access, if everything runs on 127.0.0.1 and every service shares it then they can all talk to each other! (See also network namespaces or VMs)
• Don’t reuse passwords
• keep software up to date
• actually evaluate the quality of the project if it needs access to sensitive information
• • see open issues, closed issues that stand out
• • check for audits or at least a history of good effort™

Sure you wont always catch ai slop this way but you don’t need to read a line of code to at least be reasonably sure your arr stack won’t get to the family photos.

Can’t have shit in Detroit.

Didn’t pay that, only the microwave light works now.

Don’t you mean: “How much speedtest?”

Windows snobs cant even run Windows on without a super giga 1000€ license for more than 16 Core CPUs

I’m not using Windows servers at home but if I did then a license wouldn’t be a factor when deciding what hardware to buy.

Technically, a copper wire is a battery that charges in (a very tiny fraction of ) seconds.

If you’re truly that revolutionary then more than enough people will post for you.

Are ya winning, son?

Hidden

You can just do it in parts though?

If you have a flake.lock you can update it, start rebuilding (nixos-rebuild boot) and if it’s not done before shutdown you can just run that same command after the next boot and it will continue where it left of (minus a few packages it has to rebuild again).

My pc always updates to the latest lock whenever it is running, when I update my Nixos repository my pc will eventually follow without doing anything. The only thing to watch out for is changed configurations or build errors but for that you just have to check the logs every once in a while or set up some way to be notified of the failing rebuild command.

From the moment I understood the weakness of my flesh, it disgusted me. I craved the strength and certainty of steel. I aspired to the purity of the Blessed Machine. Your kind cling to your flesh, as though it will not decay and fail you. One day the crude biomass you call a temple will wither, and you will beg my kind to save you. But I am already saved, for the Machine is immortal… Even in death I serve the Omnissiah.

https://youtu.be/M3OAx8EFtz8

https://youtu.be/4fNS9CNmIc8

But only to protect the children™ of course

You good?

While you can convert (or rather represent) an ipv4 as decimal, op indirectly stated that they were in dotted decimal notation and as such the leading 624 doesn’t work in that context.

Also shortening ipv4 is cursed, why must you share this knowledge?

Also also, curious to note that glibc parses 1 as ipv4 0.0.0.1 and not ipv6 ::1, probably because they predate ipv6.

He’s too good, I can’t trace his ip!

They should’ve traced his ipv6, while 624::/16 isn’t currently allocated, it is at least usable if we need it.

Did I miss something?

Launch multiple?