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
Being compatible is different to being compliant. Saying something is able to reach something vs being backwards compatible. Labeling something old as new is not helpful even if that's how its been
The way USB works is that *hosts* and *hubs* need to support all speeds but *devices* do not. This makes perfect sense because USB versions aren't just about speeds; a mouse can use 2.0 features without needing to run at 480mbps. This has always been this way.
I couldn't find a place in the 3.x standard that requires hosts to support all rates for that standard; this could be an oversight, but I also haven't seen any evidence of manufacturers cheating and labeling 3.0 host ports as 3.1. All the brouhaha seems to be about *devices*.
And as I said this is *normal*, makes perfect sense, was already the case with 2.0, and is how pretty much every other standard works. You don't need to support the absolute screaming fastest data rate of a standard to call yourself compliant.
Thanks for explaining that to me
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
