You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Label selector semantics were designed originally for the monitoring system. Monitoring and load-balancing systems wanted to ensure that non-overlapping queries could be constructed. Without disjunction, a common key with different values ensures two selectors don't overlap
Selectors are also simple enough they could be reverse-indexed, which could be used by watch to find outstanding queries matching labels of a new/changed resource instance. But we haven't implemented this yet in K8s (http://issues.k8s.io/4817 )
Another thing we haven't implemented yet that SREs asked for in the original design is a way to default, require, prohibit, and validate label keys and values:http://issues.k8s.io/15390
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
