Heard: native composer beats third-party thread tools for reach right now

Heard: native composer beats third-party thread tools for reach right now
Confirmed: posts created in X's own composer and posts pushed via API both reach the same timeline ranker — the source field isn't a direct input.
Rumored: but as of this quarter, scheduled-via-tool threads cluster their replies in a burst that the reply-velocity signal reads as less organic.
When to use which:
— Native composer: any post where the first 30 min of engagement matters (launches, hot takes)
— Thread tool (Typefully, Hypefury): batch evergreen content where timing is flexible
What it means for your reach: don't schedule your best thread through a tool and post it cold at 3am. Draft in the tool, fire from native at a live hour.