But, if I use a i2p only client and someone who has a client that does both leeches then they would seed to the clearnet too right?

With that i2p option. Would it be sharable with people using non-i2p connections?

Self-hosting podcast is paranoia??

A file system that reports file corruption. I believe ZFS is one of those? I’m not really familiar with how that works

What does dummy HDMI plug mean?

Okay, but how do you monitor the issues with reading and writing?

Nvidia RTX 4090 ti.

Obviously a joke. I’d love to see some good suggestions here too ☺️

Maybe a mini split would work? Though, if it has to go up I think that wouldn’t work because the lines connecting has water that has to have gravity to drain.

I couldn’t have said it better myself.

What about second breakfast??

Shrek - OPNSense, because it (firewall) guards my swamp.

Dragon - NAS, because of a dragons hoard.

Donkey - Proxmox, I use this for a few VMs and docker containers. It stores my DNS, donkey was annoying, and there is nothing more annoying than your DNS going down.

Fiona - Backup NAS - less big, only stores important backups.

I love it! Thanks for sharing!

My pixel is named iPhone… lol

Examples please?? I love this!

Crazy? I was crazy once.

It seems like that data is from 2014 as well. I’m sure the numbers would have improved in almost ten years too!

No, the creator of it-tools did. I just told you about it. Give them a star on GitHub and maybe donate if you can ❤️

Yeah, that’s going to come completely down to the containers you’re running and the people who designed them. If the container is built on Alpine Linux, you can pretty much trust that it’s going to have barely any overhead. But if a container is built on an Ubuntu Docker image. It will have a bunch of services that probably aren’t needed in a typical docker container.

Of course, but the amount of overhead completely depends per container. The reason I am willing to accept the -in my experience- very small amount of overhead I typically get is that the repeatability is amazing with docker.

My first server was unRAID (freebsd, not Linux), I setup proxmox (debian with a webui) later. I took my unRAID server down for maintenance but wanted a certain service to stay up. So I copied a backup from unRAID to another server and had the service running in minutes. If it was a package, there is no guarantee that it would have been built for both OSes, both builds were the same version, or they used the same libraries.

My favorite way to extend the above is Docker Compose. I create a folder with a docker-compose.yml file and I can keep EVERYTHING for that service in a single folder. unRAID doesn’t use Docker Compose in its webui. So, I try to stick to keeping things in Proxmox for ease of transfer and stuff.

Nice! I wonder if there’s anything one has that the other doesn’t.