4 ms·

Ugh...I have a HN Twitter bot that just tried to post this and it got locked. https://www.twitter.com/hackernewstop10 https://www.twitter.com/hackernewstop10

• hirsin 6y ago
  Oh no, I hadn't even thought of that. Yes, likely many bots locked for this.
• billrobertson42 6y ago
  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.)
• rgj 6y ago
  The reason for the ban is “revealing private information”. It seems to be related to a Dutch soccer player Memphis Depay. https://twitter.com/OL_English/status/1371121328649076744 https://twitter.com/OL_English/status/1371121328649076744
  • madars 6y ago
    Oh! When I first read the headline, I thought of Windows 98 (codename: Memphis), and got excited this is gonna be something retro about an elite UX design.
  • tom_mellior 6y ago
    I read that tweet as OL's social media team having heard of the problem and poking fun at Twitter. Nothing in that tweet suggests that there is a causal relationship with that specific person.
  • dzhiurgis 6y ago
    https://en.wikipedia.org/wiki/Streisand_effect https://en.wikipedia.org/wiki/Streisand_effect
  • Clewza313 6y ago
    Out of the loop: what genie are they trying to stuff back in the bottle? Googling reveals that his transfer contract with full prices etc was leaked, but that appears to have been a few years ago.
• artemave 6y ago
  Oh man, I'm two bots down: https://twitter.com/Hn251 https://twitter.com/Hn251 and https://twitter.com/Hn150 https://twitter.com/Hn150
• c17r 6y ago
  Yep, mine at https://twitter.com/hn_frontpage https://twitter.com/hn_frontpage got hit as well
• jl2718 6y ago
  Maybe they’re trying to get rid of bots.