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
If you read anything, from BitLocker reversing tool source to articles to FIPS reports, it says it uses AES-CCM to wrap keys. It doesn't. It uses AES-CTR. Somehow everyone has managed to write AES-CTR implementations and call them AES-CCM. WTF.
The only thing "CCM" about it is that it prepends (15 - nonce_len - 1) (so 0x02) to nonces. It doesn't use a MAC. It doesn't have associated data. And crucially, it doesn't use the first keystream block for that, which definitely makes it not CCM and not compatible with CCM.
Lol, I take that back. It *is* CCM, it's just that libbde incorrectly implements it as CTR and it works by accident (and returns 16 bytes of garbage before the plaintext). The correct ciphertext format is <12b nonce><16b tag><ciphertext>, not <12b nonce><ciphertext>.
Good to know 
there's no mention of ccm anywhere in group policies thopic.twitter.com/OCyAiMfmLG
Those are the disk encryption algorithms. "CCM-not-really" is used for key wrapping.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
