3 ms·

It doesn't appear to be locked now.

• JdeBP 6y ago
  Apparently the company has very recently tweeted that a "bug" causing this has now been fixed.
  • billrobertson42 6y ago
    Good for them. Bug, mistake, bad data, or whatever. Glad they fixed it.
  • tom_mellior 6y ago
    "The company" hasn't tweeted about this either at https://twitter.com/twitter https://twitter.com/twitter or https://twitter.com/TwitterSupport https://twitter.com/TwitterSupport. Link or it didn't happen.
    • JdeBP 6y ago
      I said "apparently" because my source was a screenshot of a tweet saying "Sorry for that.", just as this Gizmodo reporter also saw. * https://gizmodo.com/twitter-banned-me-for-saying-the-m-word-memphis-1846474378 https://gizmodo.com/twitter-banned-me-for-saying-the-m-word-...
      • tom_mellior 6y ago
        The same user later tweeted: "to the people getting mad at me for this, it's ya' own fault for believing a single tweet from an unverified source instead of looking at the official twitter pages. i'm just havin' fun." https://twitter.com/SPLLTHEMANSNAME/status/1371192195777232898 https://twitter.com/SPLLTHEMANSNAME/status/13711921957772328... So yes, unsurprisingly, something that "apparently" happened but wasn't sourced didn't actually happen.
    • ckwalsh 6y ago
      Hot off the press, it's official now: https://twitter.com/TwitterSupport/status/1371235587718582274 https://twitter.com/TwitterSupport/status/137123558771858227...
      • tom_mellior 6y ago
        Thanks. (In case people wander by later, this was tweeted half an hour after my post above, and the OP has made it clear in a parallel subthread that they were referring to something that was later admitted to be a hoax by the perpetrator.)