Analysis archive

The Number-One Slot Is More Volatile Than a Screenshot Suggests

An hourly comparison of eight Q1 2026 feeds measures how often the recorded leader changed—and where the method stops.

TG
TrendGoing Editorial
Editorial standards

The most unstable part of a ranking is often the part people screenshot: number one. During Q1 2026, the top item changed between consecutive observed hours at very different rates across TrendGoing's saved feeds. Weibo changed leaders in 49.1% of valid hour pairs; Hacker News Best changed in 7%.

This is not a comparison of audience fickleness. It is a comparison of recorded first positions after normalizing the archive to one leader per hour. The platforms use different inputs and ranking systems, and the collector does not see every update between two captures.

Share of consecutive observed hours with a different #1 item

Weibo49.1%
Hacker News Top39.8%
Toutiao37.8%
Baidu33.8%
Zhihu25.4%
Tieba19.3%
V2EX13.7%
Hacker News Best7%
Only hour pairs one or two hours apart were compared; longer collection gaps were excluded.

Why normalize by hour?

A raw capture-to-capture calculation would mostly measure our scheduler. A feed saved every few minutes gets more opportunities to register a change than one saved every half hour. We therefore kept the first non-empty observation in each hour, sorted the hourly sequence, and compared only pairs separated by one or two hours. Longer gaps were not bridged.

SourceHourly #1 change rateDistinct hourly leaders
Weibo49.1%915
Hacker News Top39.8%669
Toutiao37.8%710
Baidu33.8%704
Zhihu25.4%293
Tieba19.3%383
V2EX13.7%257
Hacker News Best7%113
Table 1. A leader is the first internal item ID in the first non-empty capture for an observed hour.

The distinct-leaders column adds scale. Two feeds can have the same change rate but a different number of items occupying first place. One might alternate between a small set; another might continuously introduce new leaders. We report both because “volatile” should not hide the shape of the movement.

A screenshot is a timestamp, not a verdict

When a publisher writes “the internet's top topic,” the claim usually outlives the evidence. A screenshot documents the first position at one moment on one feed. If that feed changes leaders frequently, the wording should include the observation time and avoid implying a day-long consensus.

For researchers, the practical response is to save rank and timestamp together. For editors, it is to revisit the list before publication. For readers, it is to treat number one as a location inside a moving system—not a direct measure of importance.

Ranking rules explain part of the difference

Baidu publicly describes an index combining search and information signals and says its hot list is updated frequently. Weibo describes a composite of search, posting, interaction, and reading signals. Hacker News exposes ordered lists of story IDs through its API. These are distinct instruments. The chart should be read as evidence about their captured output, not as a universal measure of attention.

Our next step would be to add semantic clustering so that reworded versions of one event can be treated as a single topic. This article does not do that. If a source assigns a new internal item to a revised headline, the method counts a new leader. Publishing that limitation is more useful than pretending the number is perfectly clean.

Primary references

About this analysis

TrendGoing uses public announcements and observable online signals as source material, then adds original interpretation. Analysis reflects the information available on the publication date and does not constitute financial, legal, or medical advice.

Spot an error or missing context? Email [email protected] with this page's URL.

Keep reading

More original analysis