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
They're not saying you should use plaintext, they're saying you should use something else until the bug is fixed. This is probably a remote code execution bug (or an active key disclosure flaw). You shouldn't *decrypt* (untrusted) incoming email [which could be malicious].
Seems to me what they are actually saying is that automatic decryption of incoming messages, and the handling thereof is the issue... nothing to do with transmitting / decrypting / reading encrypted messages in a "safe" environment.
I suspect the automaton possible with something like JavaScript being the culprit, and the email client's "features" bring far to cooperative... possibly linked with storing plain text after initial (and automatic) decryption of incoming messages.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
