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
40s? I wouldn’t estimate anyone the ability to deploy that quickly, let alone do root cause analysis to figure out what the leak actually is in that span of time.
I would expect them to have a killswitch for internal admin tools in case of abuse.
I’m still surprised. It takes time to detect these things & conjure meetings to decide proper course of action. Consider how such a killswitch could be abuse, and then consider what process would be put in place to mitigate such abuse... and only then weigh it against this.
Meetings? What? It's a killswitch. The whole point of a killswitch is to stop dangerous things from running amok. If your process requires meetings to respond to this kind of incident, your management has gone insane.
And some kind of warden running and watching for suspicious activity like a single DBA adding posts to many accounts.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
