u/alessandrobertulli

Hi, I'm planning to host a few services (Tailscale mesh VPN, file sharing, media streaming and password vault), aside from the VPN the server won't work 24/7, it will spend quite a bit of time idle.

Environment sustainability is really important for me, so I'm curious about which option produces less CO2. At home I have an old Raspberry Pi 3B+, an old-ish SSD and a few second hand HDDs. Or, I know that Hetzner uses often recycled servers, and powers them with 100% renewable energy (but they don't neccesarily produce 0% CO2), and they are based in Germany/Finland (I live in Italy). The cheaper option is probably the homelab, but what about in terms of CO2? Thanks!

Hi, I'm planning to host a few services (Tailscale mesh VPN, file sharing, media streaming and password vault), aside from the VPN the server won't work 24/7, it will spend quite a bit of time idle.

Environment sustainability is really important for me, so I'm curious about which option produces less CO2. At home I have an old Raspberry Pi 3B+, an old-ish SSD and a few second hand HDDs. Or, I know that Hetzner uses often recycled servers, and powers them with 100% renewable energy (but they don't neccesarily produce 0% CO2), and they are based in Germany/Finland (I live in Italy). The cheaper option is probably the homelab, but what about in terms of CO2? Thanks!

Hi, I'm planning to host a few services (Tailscale mesh VPN, file sharing, media streaming and password vault), aside from the VPN the server won't work 24/7, it will spend quite a bit of time idle.

Environment sustainability is really important for me, so I'm curious about which option produces less CO2. At home I have an old Raspberry Pi 3B+, an old-ish SSD and a few second hand HDDs. Or, I know that Hetzner uses often recycled servers, and powers them with 100% renewable energy (but they don't neccesarily produce 0% CO2), and they are based in Germany/Finland (I live in Italy). The cheaper option is probably the homelab, but what about in terms of CO2? Thanks!

Hi all, I have studied Kleene fixed point theorem during my CompEng bachelor but it passed a bit of time, so I need a refresh. I read that we use a fixed point recursion in Nix for instance to import nixpkgs, and (perhaps?) to use overlay and overrides. I tried reading this beautiful post by layus but it only partially "clicked". How would you explain fixed point recursion, and why it is important in Nix, especially in the nixpkgs case? Thanks!

Hi, I'm learning about immutable systems and naturally I came across Nix/NixOS and container/bootc. A thing I really like about Nix is that every package is cached, so that if ten "user" derivations all use the same dependency, this is shared (exactly like in a normal package manager), even if it is still immutable and "embedded" into each derivation. I half heard a similar thing happens with OCI container layers. Could you please explain the difference better? Are they shared among different images? How are they identified? How is the system sure they could be shared? Are they cached? Where? Thanks!

Hi, I'm learning about immutable systems and naturally I came across Nix/NixOS and container/bootc. A thing I really like about Nix is that every package is cached, so that if ten "user" derivations all use the same dependency, this is shared (exactly like in a normal package manager), even if it is still immutable and "embedded" into each derivation. I half heard a similar thing happens with OCI container layers. Could you please explain the difference better? Are they shared among different images? How are they identified? How is the system sure they could be shared? Are they cached? Where? Thanks!

I thought the keyboard was not being recognized during the writing of the firmware, so I gave Ctrl+C. Recently purchased Air96v2 became an expensive piece of furniture. Managed to reset with the button under caps lock, but now writing the new firmware is taking ages. Is this normal?