A decentralized Twitter?
Andrew Baron is a smart guy, and he's not a techy, so when he explains technical issues he does it in a way non-technical people can understand. — Dembot: “If you hosted your own Twitter, just like you host your own website, you could put your twitter anywhere.”
Context & Ripple Effects
Twitter has spent months making the case against itself on reliability grounds: a twelve-hour outage in mid-December 2007 drew commentary on whether such a basic service can be trusted, and on January 15 the entire network went down during Steve Jobs' Macworld keynote, cutting off updates for thousands of followers in real time. Scripting News had already been asking since March 2007 how deliberately minimal Twitter's design really is.
Into that vacuum steps Andrew Baron — a media figure, not an engineer — arguing on his Dembot blog that Twitter should work like websites do: anyone could host their own instance and move it anywhere. The framing landed widely for a single blog post, with same-week pickups at ZDNet's Between the Lines, louisgray.com, and Publishing 2.0 turning it into a running debate over centralization versus the value of a shared network.
First-order effects
- Baron's proposal directly targets Twitter's single point of failure exposed by the January 15 keynote outage: if accounts were hosted independently, one company's infrastructure collapse would no longer silence every conversation at once.
Second-order effects
- A self-hosting model shifts the cost question that analysts were already raising about Twitter's unsustainable business model onto individual operators and hosting providers, creating a potential market for turnkey microblogging installs while stripping Twitter of its role as sole gatekeeper.
Third-order effects
- If portability becomes the expectation, microblogging converges with the web's own architecture — identity and content owned by users rather than platforms — forcing services to compete on features and trust rather than lock-in.
The trend: Social messaging is being pushed toward federated, user-hosted infrastructure, with repeated central-platform outages acting as the recurring argument for decentralization.