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
So I'm now trying to replay the capture and turns out they do seem to use something more clever than I expected. Even if I send the same 64 bit from a capture, the device sends over a different message, with what looks like two separate 64 bit values that are different.
If you know it's DES and the exact mode and don't have the key, you can crack the key for $30 at http://crack.sh . might get a bit pricy if you're guessing the format/parameters though.
Unfortunately I can only _guess_ it's DES. What I have is (at least) 64-bit sent Host→Device and at least 2×64-bit sent Device→Host right now. I was trying to set up a second VM just to see if the parts I see constants are really constant, or generated at install.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
