Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Apparently the company has very recently tweeted that a "bug" causing this has now been fixed.


"The company" hasn't tweeted about this either at https://twitter.com/twitter or https://twitter.com/TwitterSupport. Link or it didn't happen.



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.)


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-...


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/13711921957772328...

So yes, unsurprisingly, something that "apparently" happened but wasn't sourced didn't actually happen.


Good for them. Bug, mistake, bad data, or whatever. Glad they fixed it.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: