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’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.
The only abuse you could inflict with the killswitch is delaying account admin actions, which is an entirely reasonable response to abuse and a feature you must absolutely implement if you have user access tools like this.
It's common sense that any time you're mutating user data or viewing private user data, you audit the hell out of everything so you can immediately respond to abuse and revert it, and lock out the attackers. They should've had alerts for this kind of thing too.
broken management or not, how do you balance the ability to cripple production systems with these features behaving as a killswitch for legit emergencies? (I’ve seen plenty of broken management, and that may bias how I’d perceive this)
Again, it's a killswitch *for an admin tool*. There is zero user impact to using it, and no excuse for it to not exist. At most some support tickets might take longer to resolve. No reason not to have a ton of safety nets around internal tools that can take over accounts.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
