Oh, forget the fork wars. You just can't build secure applications with the OpenSSL (1.0.2?) API. Inconsistent and undocumented.pic.twitter.com/px5UWNdvX2
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
Furthermore, with OpenSSL you can't even be sure GENERAL_NAMES_free() is what you'd use in version 1.0.2a (zero API/ABI compatibility).
unfortunately LibreSSL didn't get so much traction (only BSD?), but 99% of Linux distributions/C/C++ SW are based on OpenSSL for EVERYTHING
think about Apache, cURL and thousands of projects using OpenSSL as dependency.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.