Why Twitter is such a big deal (2009)

Assessment of the 2009 “Twitter as protocol” idea

• Many commenters call the essay “wrong” or “dumb” on the narrow claim that Twitter is a new protocol comparable to TCP/IP, SMTP, or HTTP.
• Others argue it was “directionally right”: Twitter did become extremely influential and functioned like a protocol layer for social messaging, even if the technical wording was sloppy.
• Some note that in 2009 Twitter’s open API, firehose access, and third‑party clients made the “protocol” metaphor more plausible than it looks in hindsight.

Protocols vs platforms

• Strict view: a protocol is an open standard anyone can implement; Twitter was always a proprietary platform, so calling it a protocol is simply incorrect.
• Broader view: “protocol” can be used conceptually for an emergent, widely used messaging pattern; by that looser definition Twitter was a new modality (public-by-default short messages, no explicit recipients).
• Several point out that earlier media—message boards, blogs, Usenet, NNTP, multicast, even radio/TV—already had “broadcast without specifying recipients.”

Shift from open protocols to corporate ecosystems

• Timeline commonly placed around 2000–2010 with the rise of Facebook, LinkedIn, centralized forums, and mobile app stores.
• Proposed causes:
  • Convenience and usability vs the fiddliness of self‑hosting and raw protocols.
  • Better discovery and integrated UX on platforms vs fragmented standards and “protocol stasis.”
  • VC funding and ad models favoring lock‑in and large-scale moderation.
  • Search engines (especially Google) deprioritizing small sites and killing RSS/Usenet, weakening the open web ecosystem.

Why Twitter/X felt different

• Seen as “realtime news” and a public firehose: heads of state, journalists, celebrities, and ordinary users all in one venue.
• Public-by-default and low-friction short posts created a different “vibe” from Facebook’s friends-first feed or Instagram’s highly produced posts.
• It became a key support/announcement channel for companies and governments, sometimes effectively the only timely source.
• Later changes—login walls, algorithmic feeds, link suppression, ad/engagement optimization, and content moderation drift—are widely viewed as enshittification and loss of utility.

Decentralization, ActivityPub, and alternatives

• Several argue the “Twitter as protocol” dream is now better embodied by ActivityPub and the fediverse (Mastodon, Lemmy, Pixelfed, etc.), precisely because they aren’t owned by a single company.
• Concerns remain that Mastodon’s dominance and implementation quirks risk turning AP into “whatever Mastodon does,” and there is interest in more generic AP clients that unify social feeds (microblogs, photos, forums, blogs).
• Others are skeptical that “decentralized Twitter” is compelling; they expect decentralization to matter only when it clearly solves real problems (e.g., censorship resistance, anonymity, or removing middlemen).

Broader social and economic reflections

• Some see the move from protocols to platforms as an almost inevitable outcome of capitalism, network effects, and human preference for convenience.
• Proposed remedies range from antitrust and regulation to niche communities embracing open protocols, with little optimism for a full return to a protocol‑first mass internet.