How to Follow a Breaking News Thread on X Live

A breaking news thread on X updates faster than the page can keep up with, and the default "best" sort makes it worse: it ranks replies by engagement, not by when they happened, so the reply order can lag several minutes behind the actual story. Switch to newest sort the moment a thread turns live, and treat everything below the fold as still-developing rather than settled.

Why a live thread behaves differently from a normal one

Most threads settle within an hour or two — the interesting replies surface, the ranking catches up, and reading it later in "best" order works fine. A breaking thread never gets that settling time while you're watching it. New replies land every few seconds, each one competing for likes it hasn't had time to earn yet, so the ranked view is always describing a version of the thread that's already a few minutes old. How X ranks replies covers the scoring in more detail, but the short version for a live story is: ranking needs time to work, and a breaking thread doesn't give it any.

There's also a volume problem that a normal thread doesn't have. A typical thread might pick up a few dozen replies over a day; a genuinely breaking one can add that many in a single minute once enough people notice it. That pace changes what "reading the thread" even means. On a normal thread you can reasonably expect to see everything. On a live one, you're sampling a stream that keeps growing while you read it, and the goal shifts from "read it all" to "stay current without losing the thread of what's actually being reported versus what's just reaction."

When to bail on newest and check best instead

Newest sort is the right default while a story is actively unfolding, but it has a blind spot: it treats every reply as equally worth your time, and on a fast thread most of them aren't. There's a point — usually once the initial burst of activity slows and replies are landing every minute or two instead of every few seconds — where switching back to best for a moment is worth it. That's when ranking has finally had enough time to do its job, and the reply that actually added the missing detail or the correction has had a chance to rise above the noise. Checking too early defeats the purpose, since a reply posted ninety seconds ago hasn't collected enough engagement to rank anywhere near the top yet.

The manual way: newest sort and manual refresh

The standard move is to switch the reply sort from best to newest the moment a thread goes live, then refresh periodically to pull in new replies. X also shows a "new posts" prompt at the top of the timeline when enough new activity has landed — tapping it inserts the new replies without a full reload, which is gentler on your scroll position than refreshing the whole page.

Where it breaks down

Newest sort solves the ordering problem, but not the friction around it. Every manual refresh risks dropping you back at the top of the thread, and if you switch back to best sort later to see what actually rose to the top, you lose your place in the chronological read entirely. On a thread with real volume — a launch, a verdict, a live event — you end up toggling between the two views repeatedly, refreshing, and re-finding where you left off each time, which is the same round-trip problem covered in reading long X threads in order. If you also open the thread in a new tab so your main timeline stays put, you're back to the tab pile that following a live story tends to create.

The other issue is noise. The first wave of replies on any breaking thread is mostly reaction — short takes, jokes, restatements of the headline — and it's disproportionately loud because it lands before anyone has had time to add real information. Reading newest sort in real time means wading through that wave before the replies that actually add something start to appear.

A repeatable routine for a live thread

1. Switch to newest the moment it goes live. Don't wait for the thread to feel busy — ranking lags from the first reply, not just once volume picks up.
2. Mute obvious spam keywords early, the same habit covered in muting keywords and accounts to reduce X noise, so the first reactive wave doesn't drown out real replies later.
3. Treat the first ten minutes as reaction, not reporting. The earliest replies are rarely the most informative ones; they're just the fastest.
4. Check best sort after the story slows down, once ranking has had time to catch up and actually surface the reply that got it right.

The SkimFast way

Switching sort orders and refreshing by hand works, but each switch on X's own page reloads the view, and following a live thread means doing that over and over for as long as the story is unfolding. SkimFast opens the full reply thread in a popover right in your timeline, sortable between newest and best without a page reload, so watching a live thread doesn't cost you a new tab or your scroll position every time you check for updates.

A live thread is the clearest case where SkimFast earns its keep: the story is moving, you're checking back often, and every extra tap between you and the newest reply is a tap you'll repeat a dozen times before the thread settles.

The takeaway

The default ranked view is built for a thread that has had time to settle, and a breaking story never gives it that time. Sort by newest, expect the first wave to be mostly noise, and save the ranked view for once things calm down. When the back-and-forth between sorting and refreshing gets old, SkimFast keeps the whole thread — live or settled — in one place so you're not rebuilding your scroll position every time something new lands.