Changes to Twitter have yet to cease since Elon Musk’s acquisition.

Banned Journalists

In case you missed it, Twitter Spaces — the platform’s live audio feature — was disabled after the Tesla CEO joined in on a conversation where there were banned journalists, TechCrunch reports.

The journalists were indefinitely restricted from Twitter after previously reporting on the Elon Jet — a Twitter account that tracked Musk’s flights — which was banned for using “publicly-available data.”

Although the journalists had been banned from Twitter, they discovered that they were still able to voice their opinions and thoughts via Twitter Spaces.

The group included BuzzFeed’s Katie Notopoulos, the Washington Post’s Drew Harwell, Mashable’s Matt Binder, and Jack Sweeney — the journalist behind the Elon Jet Twitter account — according to the outlet.

Elon Musk Joins The Audio Chat

After learning that the journalists were still able to access Twitter Spaces, Musk joined them for the audio chat. Musk doubled down on blasting the journalists for both sharing his private jet’s real-time location and covering it in the media.

“As I’m sure everyone who has been doxxed would agree, [showing] real-time information about anyone’s location is inappropriate,” Musk said on the platform. “I think everyone on this call would not like that to be done to them.”

“There is not going to be any distinction in the future between journalists and regular people,” he continued. “Everyone’s going to be treated the same. You’re not special because you’re a journalist. You’re a citizen … No special treatment. You’re doxxed, you get suspended. End of story.”

In response, the journalists had their own critiques of his actions

Harwell claimed that he never posted Musk’s address and called out his hypocrisy. Then, Musk quickly left the chat a little while after.

In less than no time, Twitter Spaces stopped functioning accordingly.

What's The Update On Twitter Spaces?

A Twitter user questioned what happened with the feature to which Musk responded, “We’re fixing a Legacy bug. Should be working tomorrow.”

As of this writing, it hasn’t returned.