New microsyntax for Twitter: three pointers and the slasher
Image based on Kevin Van Aelst's original. — Since it's apparently all the rage to design your own features for Twitter now, I figured I'd build on my success with the hashtag and crank out a few more.
Context & Ripple Effects
This proposal extends a lineage the author himself started: he is credited with popularizing the hashtag, and his argument here is that Twitter's most useful syntax keeps arriving from outside the company rather than from its product team. The tension is old — Scripting News was debating whether Twitter should carry structured payloads at all back in September 2007, when critics argued the service worked precisely because of its minimalism.
Since then the vernacular has only thickened: @replies, retweets and hashtags became de facto standards long before any official spec, and the NYT's Bits blog codified the mess into a tweet anatomy style guide in February 2009. Proposing 'three pointers' and 'the slasher' is a bid to keep that bottom-up channel open — users designing features the platform may later have to ratify.
First-order effects
- Early adopters and third-party client makers get two candidate conventions to parse or ignore — adoption depends entirely on whether search tools and power users start honoring them, not on any Twitter announcement.
Second-order effects
- If usage spreads, Twitter inherits another fait accompli like the hashtag: either formalize the syntax into search and display, or let third-party clients differentiate by supporting what the core service does not.
Third-order effects
- The pattern points toward platforms treating user-invented notation as unpaid R&D — feature roadmaps increasingly ratified after the fact from community behavior, with the company's role shifting from designer to standards body.
The trend: Social platforms are drifting toward bottom-up protocol design, where community-coined syntax becomes official feature set once adoption makes ignoring it costlier than endorsing it.