Twitter-proxy: Any Interest?
The stories of twitter going down frequently don't need repeating here. Instead, I want to ask the community if there is any interest in addressing the problem. — As many are aware, Twitter's problem with scaling is not RoR, it's not [Joyent] NTT, or …
Context & Ripple Effects
Twitter's reliability problems were already visible in an earlier account of Twitter trouble, and outages have become more consequential as users treat the service as a channel for political discussion. The move off Joyent's infrastructure did not end the availability issue, focusing attention on scaling architecture rather than any single host.
Assetbar's proposed proxy approach frames reliability as an ecosystem problem: preserving access to Twitter's communications stream when Twitter itself is unavailable, rather than claiming to repair Twitter's core service.
First-order effects
- Twitter users and third-party developers gain a possible continuity layer during outages, reducing the immediate cost of losing access to the service.
- Twitter faces pressure to make its service usable through intermediaries if proxy tools become the practical fallback for its audience.
Second-order effects
- Joyent, NTT and RoR become less useful as sole explanations for failure when an external proxy can mask outages for users, shifting scrutiny toward Twitter's end-to-end resilience.
- Third-party tools can capture more of the user relationship during downtime, giving reliability-focused services a reason to build around Twitter rather than merely distribute its updates.
Third-order effects
- If proxy services become a durable response to recurring outages, Twitter's value chain may split between the network that originates messages and intermediaries that guarantee access to them.
The trend: Repeated platform outages are creating an opening for third-party continuity services to compete on trust and availability around a communications network.