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
The problem with FBE and all the DE stuff (and what iPhone does too) is that it's quite secure if nobody made any mistakes all the way through the stack; everything has to work together perfectly. A security flaw could make the whole thing moot, as we've seen many times.
With FDE I know that the storage is cryptographically bound to the long and not crackable passphrase, period. As long as the much simpler code from that to the storage crypto is secure, if my phone is off, you aren't getting any data out of it.
I see what you mean. At least the relevant code is open source.
It isn't. The Qualcomm bootloaders aren't open source and are in the critical path; also the *other* thing they put into TrustZone is DRM blob nonsense (Widevine) and *that* is also exploitable (and then you can escalate). See e.g. https://googleprojectzero.blogspot.com/2017/07/trust-issues-exploiting-trustzone-tees.html …
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
