Twitter recently strengthened its abuse and hate speech controls to make the platform more intuitive and desirable for users. It has since been suspending accounts posting inappropriate content or trolling others in a jiffy. But in a hilarious unexpected turn of events, Twitter suspended its own co-founder and CEO Jack Dorsey from the platform — though, only for about 15 minutes.
But, as usual, Twitter users and (of course) trolls were quick to take notice and respond with their own objective puns for the removal of the CEO from the service. In just fifteen, they surely had a lot to share about the same:
The CEO of Twitter, Jack Dorsey, has been suspended and now nothing makes sense pic.twitter.com/PwHp5rjES1
— Jared Wyand ?? (@JaredWyand) November 23, 2016
— Mark Dice (@MarkDice) November 23, 2016
The suspension of the co-founder’s Twitter account was completely unexpected as he hadn’t posted anything offending or abusive. But this got me thinking (and several other reports also speculate) that the co-founder’s social media account could’ve ben under a cyber attack. And the teams thought it was better to completely shut down the account instead of making the performance public.
Finally, Jack Dorsey’s profile, who operates under the username @jack, was brought back from the suspension lockup and reinstated in its true glory. In the following tweet, the co-founder announced his return and said that his account suspension was an internal mistake. It also paid tribute to his first-ever tweet, when the platform was called twttr.
just setting up my twttr…again (account suspension was an internal mistake)
— ??jack (@jack) November 23, 2016
In the initial moments, when the profile was resurrected, his account wasn’t showing the complete follower count of 3.9 million. And even after being restored fully, it didn’t. The micro-blogging platform’s CEO has somehow lost half a million followers in the process, which isn’t good news for other users on the platform. I would not like to lose my precious 850 followers due to an internal error. Sorry, Twitter!