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
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.
As I replied to your other tweet thanks for explaining a part of it. However this tweet here is a fallacy. And just because a new technology is made to to be compatible with an old doesn't mean it should be relabeled as the new one and if that's not happening,thatswhatpeoplethink
But as I said there's no relabeling. A new speed was added, so that means a new version of the standard. The standard isn't some standalone thing, it's literally just an update to the prior standard, so it retains all the existing options.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
