In prod, let's say you run workloads in Firecracker VMs. You have plenty of headroom on your existing hardware. Nested virtualization would allow you to set up Firecracker hosts on your existing hardware.

Home Assistant does a surprising amount of Disk I/O, if for nothing than for logs. Sibling commenters are also advising not running it on the SD card to avoid wearing it out, so there's definitely some truth here. This means we're adding a Pi M.2 hat + SSD into the mix. The Pi5 SSD kit for 256 GB, when it was available, was around $60 USD. A Pi5 with 8 GB of RAM is $130 USD. Now we need a cooler, a case that will fit the Pi5 with said M.2 hat, and a power supply. We're already well north of $250 USD, encroaching on $300, and we're not even using the core benefits of the Pi's platform. No need for GPIO pins, tightly integrated cameras or other sensors, none of that.

For all we know, the blog author did this assessment (or trusted the assessment of others, eg: Jeff) and came to the came conclusion - it wasn't worth the price of entry.

^1: https://www.jeffgeerling.com/blog/2025/intel-n100-better-val...

I think it's reasonable for Zulip to ask for compensation for access to these gateways, since Apple and Google do not make them available to end users free of charge, and the burden of responsibility to ensure that these systems aren't abused is on them. Also, the fact that they offer mobile push notifications for any self hosted server of up to 10 users is pretty generous, and there seems to be a Community plan option for larger servers that includes "groups of friends" as a qualifier. It really seems they're offering quite a bit.

Would it be handy to have this all in one cable on both ends? Sure, absolutely, that'd be killer. I personally don't think it's too big of an ask to use two cables in an installation or recovery case though, and if your devices only have USB-C ports for video out, an active USB-C to HDMI via DP-Alt cable can be had to meet that need.

[0] https://wiki.sipeed.com/hardware/en/kvm/NanoKVM_USB/introduc...

[1] https://www.cytrence.com/product-page/cytrence-kiwi

Maybe that doesn't move the needle on whether they're a small non-profit or not for you, but it's different than a massive non-profit like, say, the Prevent Cancer Foundation, which also receives millions of dollars per year to facilitate their mission.

Not every idea that rethinks an existing system will have the same merit or success of course, but I think it’s fair that sometimes a potential user will say that they think their existing system is fine and that others should adopt it vs consider something new.

Worthwhile to also mention that ISDN was full duplex, instead of half-duplex like dialup. The modems on either end would need to time-slice to allow bi-directional communication, which in a TCP laden world like the web meant that every interaction was orders of magnitude more latent than on ISDN, in which you had symmetrical, full-duplex 56k of bandwidth between you and the ISDN modem. That's the biggest reason why you had a significant decrease in latency.

I'm a Pulumi user myself, and I haven't seen a Pulumi provider for Incus yet. Once I get further into my Incus experiments, if someone hasn't made an Incus provider yet, I'll probably go through the TF provider conversion process.