Even if Twitter loads 20 tweets, it doesn't mean you've read 20 tweets.

This is not semantics, as tweet impressions are a separate metric Twitter tracks and would more intuitively represent reads.

Unless Twitter engineering did some malicious compliance for Elon.

Personally I wouldn't assume that the app that's been demonstrated to count "views" in extremely sketchy ways has suddenly started caring about the distinction between loading and reading a post. Especially when the intent is pretty obviously to herd users towards subscribing.

Fair counterpoint: Tweet views are a vanity metric (which is why Elon likes them), but tweet impressions are a required metric for advertisers to track ad CTR and any shenanigans there will actually kill Twitter.

If the point is to stop scrapers, they would _have_ to use “tweets fetched” as the metric.

The bullshit reason given for this was to “prevent bots and scrapers”, so I strongly suspect they’d be using API responses, rather than impressions.

Especially so considering how quickly some people are reporting the rate limiting impacts them