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
Idea: Allow using a SRV record to specify a different host/port which the CA will then verify with http-01. That way you don’t need dynamic DNS. Drawback: some consumer DNS hosts might not let you create SRV records…?
That sounds reasonable. Another option discussed on m.d.s.p is to use TLS NPN (e.g. 'acme') as an assertion that the server is secure. This requires code changes though.
Silly idea: a method where the server tells you what IP address it’ll be verifying from, and you add an iptables rule based on source IP
I think part of the rationale for not publishing validation IP addresses and potentially having them be unpredictable is to hinder e.g. BGP attacks to partially hijack the routing of a given IP.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
