I start my streams with a few minutes of a "starting soon" card with some chill music playing in the background. that gives me time to settle and be like "ah shit I've pushed the Go Live Button better buckle down and do something" so I'm not immediately going HEY GUYS WELCOME BACK WTF AM I DOING.

You should have used Option tho. Option can allow max one. Vec allows resizes at runtime.

Wish there was way you (tailnet status) can give a hint. Maybe ping latency for each DERP relay (probably better than trying to GeoIP/distance calculations), imagine if localapi included this info, refreshed every packet sent, a la webrtc internals.

This was very important information. Thanks. I think the "priority" way of thinking is better than "filter" way of thinking. Give priority based on rules, but do try others, as rules are not 100%.

Can I presume that if the "internet" internet is down, but peers are on same net (and have once discovered each other), they will keep seeing each other (via localapi) for the duration the internet is down (even days?)?

Cool, you are actually making the case for tailscale status here, I only want to discover services I can connect with. Also I have connectivity check (dont talk to peer that's being relayed), which is a peer to peer information and not available via API I presume.

Can I assume the key would be missing / null if I have direct connection with a peer?

Also what is the type of `Relay`, as is String, or really Option<String>. The devices I have all are using relay, but I am trying to figure out how to programmatically check connection type to peer.

I guess they call it lifetimes cause it takes a lifetime to figure it out