You're probably talking about this HN comment [1], but he was typing in the command wrong, and thus not querying it without a User-Agent (important, as Twitter has known different behaviour with different UAs), and once he got it right - same behaviour [2].
Like, sure, it could be a weird technical glitch. But as of yet, nobody could find a counter-example of a web property Musk didn't have an issue with, where this behaviour was exhibited.
[1]: >>37136776
[2]: >>37139792