Twitter Announces Custom Timelines For Hashtags Or Topics On Tweetdeck, Launching API Too
Twitter will let you create custom timelines based on topics, hashtags and more from Tweetdeck, it announced today. Twitter is also providing an API to allow developers to build this functionality into their products.
Context & Ripple Effects
Days after filing its IPO registration on November 9, 2013 — with underwriters reportedly eyeing a price above the confirmed $23–$25 initial range, though that higher number remains unconfirmed — Twitter is rolling out custom timelines built around topics and hashtags inside Tweetdeck, plus an API so outsiders can build the same thing. The pickup was unusually broad for a product note: AllThingsD framed it as 'the future of Twitter events,' and The Verge, ReadWrite, The Next Web and Marketing Land all ran the same-day announcement.
The strategic read is that this is an engagement-and-distribution move by a company positioning itself as a publicly traded advertising business. Handing media partners free curation tooling gives broadcasters and publishers a reason to assemble coverage on Twitter itself rather than merely embedding tweets elsewhere.
First-order effects
- Editors, event organizers and brands can now assemble live coverage columns around any hashtag directly in Tweetdeck, replacing manual curation with a first-party tool.
- Developers get official API access to embed custom timeline functionality in their own products, shifting topic curation from copy-paste widget work to programmatic integration.
Second-order effects
- Third-party curation and social-listening tools that charge for hashtag aggregation suddenly compete with a free native feature from the platform owner.
- Curated event timelines strengthen Twitter's pitch as the second-screen companion for television and live events — the framing syndicated coverage like AllThingsD led with.
Third-order effects
- If the model holds, the single shared timeline fragments into many programmable surfaces — which forces Twitter, now accountable to public-market investors, to choose between keeping the API open and protecting its advertising-driven revenue concentration.
- A successful developer-built timeline ecosystem would make curation a platform primitive, pushing rivals to expose comparable APIs or risk becoming raw content suppliers to Twitter's surface.
The trend: Real-time platforms are splitting the single chronological timeline into many curated, developer-built surfaces, with the platform owner's API openness deciding who gets to do the curating.