What's your contingency plan for someone using your service to process abusive/illegal content? It seems difficult to manage that scenario if it's a side project, and could easily get your API access banned.

You're thinking of Tailscale.

It's trivial to debloat with an unattend.xml during install or the various debloat tools.

Plenty of fish in the sea. The odds are low.

Committing accepts all changes for me, and has for as long as I can remember.

There are situations when this is not the case case for sure.

My workplace has a very similar culture and nobody works 996.