Twitter plans to have shareholder vote by August on sale to Elon Musk

Twitter will have a shareholder vote to decide if the company should sell to Elon Musk for $44 billion


Reuters June 09, 2022
Musk, a prolific Twitter user, has said it needs to be taken private to grow and become a genuine platform for free speech. PHOTO: REUTERS

Twitter Inc anticipates a shareholder vote on its $44 billion sale to Elon Musk could come by early August, as it continues to work constructively to complete the deal with the world's richest person, the social media company's top executives told employees on Wednesday.

Musk's lawyers warned Twitter on Monday that he might walk away from the acquisition if the company fails to provide the data he seeks on spam and fake accounts. 

Twitter has said it is continuing to share information with Musk. Part of that data is the "firehose," a set comprising all tweets on the platform analyzed by different parameters, such as devices of users or profiles of accounts that publish tweets, according to people familiar with the matter.

Twitter sells this data to social media monitoring companies as part of its licensing business but plans to furnish it to Musk for free as part of the information exchange, the sources said. The firehose does not contain confidential information, such personal details of Twitter users that are not public or how often they verify their accounts, the sources added.

Twitter Chief Executive Parag Agrawal last month tweeted he did not believe a calculation of fake and spam accounts could be performed outside the company, because it would require private information that Twitter cannot share.

It was not clear how much confidential information about its user base Twitter will share with Musk. The Washington Post first reported on the sharing of the firehose.

A Musk spokesperson did not immediately respond to a request for comment.

 

 

 

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ