JavaScript boy and “lovely thoughtleader” 
he/him 
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
This particular message is from the DOM, not Firefox or its DevTools. InvalidStateError (code 11) is a DOM core error. Chromium Blink has this "...use an object that is not... usable" message, too.
https://github.com/chromium/chromium/blob/6efa1184771ace08f3e2162b0255c93526d1750d/third_party/blink/renderer/core/dom/dom_exception.cc#L66-L68 …
https://github.com/mozilla/gecko-dev/search?q=NS_ERROR_DOM_INVALID_STATE_ERR&utf8=%E2%9C%93 …
https://github.com/chromium/chromium/search?utf8=%E2%9C%93&q=DOMExceptionCode%3A%3AkInvalidStateError …
I know it's from Firefox. I'm blaming devtools because it's the only real place where errors are going to be surfaced to the developer, so the expectation there is that they own the experience. Distinction doesn't really matter about whether it lives in the DOM or not.
I replied with a comparison between Chrome and Firefox. Just because the spec has a shitty error message doesn't justify Firefox having it.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
