so an internal service would be considered public if it's reachable over https (which should ideally be the case) and the service has a valid cert for some name in public DNS that points at it? overloading TLS cert meaning with "I trust the owners of these domains"?
-
-
so it won't provide any of the desired benefit for a long time, and at the same time, you're adding a big heap of new complicated infrastructure and security policy changes on the client?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Nah, this is identical. You'll be able to measure the incremental difference in a service's monthly bandwidth costs, which will scale down linearly with client adoption. No large stair-step! As good as this sort of thing gets, TBH
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
