I've used Rongta thermal printers a fair bit, I've found them to be cost effective and easy to use. I mostly use them via WebUSB and some random JS ESC/POS lib.
Though I have never bought directly from Rongta.
> What would you want them to do if the tables were reversed?
While I understand this sentiment - is that really how you create a successful business?
If you have a worker who just doesn't perform at all, no matter what you do, should you fire them? Would you want to be fired if the tables were reversed?
I self host a lot, including some business related infrastructure for my home office (some employees also work from here).
However services designed to be accessed by a wider public audience (eg; websites, emails, Nextcloud) are hosted on a rented dedi.
As other comments have pointed out, kids suck up every minute of your life, and when the internet or Plex don't work I'll know about it real quick (DAAAAD!).
The important question for me is; how fast can I rebuild all of this if all the drives were wiped?
* Rundeck container for various infrastructure based automation jobs
* Zabbix + Grafana containers for monitoring
* PacketFence VM for NAC
* Shinobi container for NVR
* Snapcast container for multi-room audio
I also have plenty of containers and VM's for various testing apps, or dev projects.
All of my non-critical containers (eg; Plex) self update daily at early morning hours.
For the critical stuff, I have tried to automate updates as much as possible.
The majority of things can be recreated from ansible, docker compose, or Nomad scripts, all of which are backed up to an offsite Nextcloud instance.
I use a lot of services on Opnsense, but I think one of the most important for me is the Traffic Shaper, allowing for bandwidth control.
I have about 14 VLAN's, and am in the process of setting up VXLAN's for further isolation.
I use restic for encrypted backups, stored in Wasabisys.com (no cost to download, unlike Backblaze).
I will admit there is still one design flaw that I'm yet to spend time overcoming; if everything is powered on at the same time, there is a chance some devices won't get an IP because OpnSense is not yet ready.
My current flawless work-around is to boot Opnsense 30 seconds before everything else.
This already exists. For a project I worked with a 'house of the future' style project. Which was build in a way that it was a faraday cage that had an option of letting selected frequencies through.
It’s mostly Americans, because this opinion has no basis in facts. China hasn’t invaded anyone in decades, repeatedly says it won’t, and even written this down in their constitution.
Far too often I build a project, only to get ready to deploy it, then struggle to think of a name/domain for it.
Then coupled with the thought of struggling to market the project, I end up fizzling out at that stage.
If I already have users of the project, then I'll deploy it as a subdomain and forget about it until a user complains.