Add ability to choose a custom coordination server

Short-term (<15minute, repeatable) hush modes are considered a safety feature. They prevent angry homeowners from removing the smoke alarm entirely, a far more dangerous situation than a short term hush.

NFPA 72 recommends a desensitization method for ionization smoke alarms and requires one for smoke alarms installed near a cooking appliance, and several states have followed in codifying this into law. Hush is not required for photoelectric smoke alarms, under the theory that they are less prone to cooking and shower-related false-positives, but this feature is still allowed and they are a common user convenience.

UL 217 allows smoke alarms to be provided with a <15 minute desensitization feature which prevents an alarm from triggering unless obscuration/ft exceeds 4%.

Also... the Nest v2 got an in-app hush feature. My understanding is that V1 had some kind of false-positive issue that triggered a ">4% non-hushable" alarm, though, so this wouldn't have mattered.

Bogle (the father of the index fund) talks about how the index fund and friends has warped the benefits of ownership to leave companies effectively "unowned".

This can be true in VC-backed private companies too, but with public companies it seems to be even more amplified since the investors unlike angels/VCs often don't even know let alone care what the company really does.

I also believe that traffic inside homes should be secured regardless since routers can be hacked. So in my case, I didn't consider it a duplicated effort. I had my traffic already encrypted and authenticated when I started using Tailscale.

But nothing against keycloak - keycloak is the gold standard. But compared to Authelia, Keycloak is really cumbersome to get up and running and also to maintain.

In general the OSS operating systems get OSS clients, whereas the closed-source ones don’t necessarily get the full OSS treatment.

Mostly because developing for iOS and macOS is terrible, especially when your app needs to have "entitlements". Tailscale uses a "Network Extension entitlement" which is linked to our corporate Apple account. Even onboarding new employees and getting them up to speed on xcode/macOS/iOS development is painful. It often requires a bunch of messing around with Keychain and random reboots (not just Xcode restarts!) because something in the macOS kernel gets confused. For some development we also need to disable System Integrity Protection. And make sure there aren't duplicate copies of certain files between /Applications and ~/Library/Developer/whatever.

And then once you get it all working, some cert or login or something in Xcode or Keychain expires in a few months and you have to re-learn the whole esoteric dance once again.

The whole process of developing Network Extensions is pretty terrible.

Even if we open sourced it, you couldn't just git clone it & hit play in Xcode. Even if you paid Apple $100/year, you still couldn't, because your Apple account isn't blessed enough with the right to use a Network Extension.

It's hard enough for us to support Apple platform development internally without helping the world learn Xcode/code signing/entitlements/Keychain.

I've been and remain a huge open source fanboy for about 25 years now. If I thought we or the community would benefit from it being open source, I'd argue for us open sourcing it. But it just doesn't seem worthwhile. Or maybe I'm just still angry at the platform.