5 ms·
For a year or two I've predicted the ultimate demise of Twitter, which probably means some kind of acquisition. I stand by that prediction. They have hundreds o
by cletus 14y ago
For a year or two I've predicted the ultimate demise of Twitter, which probably means some kind of acquisition. I stand by that prediction. They have hundreds of millions (if not billions) so it's not going to happen overnight but it will happen.
What is Twitter? I see it as two things:
1. Infrastructure: it is a means of sending thousands of short messages a second to people in asymmetric relationships. Technically this isn't a hard problem. There are many companies around who handle traffic many orders of magnitude above this. The danger with infrastructure is that it will get commoditized. The cost in terms of resources (bandwidth, CPU, power) is not that high;
There are parallels between Twitter and SMS. SMS survives and is hugely profitable because of the telco cartel that monopolizes it. Where hosting companies will provide you with bandwidth for cents per GB, SMS costs thousands if not millions of dollars per GB. That too will come to an end eventually. What saves it now is all the players want to push their own standards and they aren't interoperable. It's IM fiefdoms all over again.
2. An audience. Twitter and its users have the ability to reach a large number of people. Originally Twitter was envisioned as a means of real-time status updates between normal people. My impression is that this use case is basically dead. The vast majority of Twitter usage seems to be as a communication tool by celebrities. There is a business in that but it isn't the revolutionary communication tool it was once thought (and some still think) it to be.
So the camps in question (the API camp and the ad camp) fit into the above.
Owning infrastructure can be hugely lucrative (eg SMS). History is full of examples of this. Railroads, oil, telephony, etc. The problem is that you get too big and the government will intervene.
Messaging infrastructure is too important for one party to own it. Email is federated and open. The future of messaging is too (I believe) federated and open.
So that leaves (2), the ad camp. The problem with advertising on Twitter is the same as it is on Facebook: it's an unwelcome intrusion.
Perhaps Twitter could have (and may still be able to) build a display ad business but Twitter is still not a particularly mainstream product (and IMHO it doesn't look like it ever will be).
Perhaps Twitter could've had a subreddit/Facebook pages type hubrid model. Upvoting of Tweets is possibly interesting.
Of course this faces the same problem Digg had: few things are globally interesting. What's interesting to you is not necessarily interesting to me so you changing what I see is again an intrusion.
Basically "content gateways" (like Digg, Slashdot, etc) were I believe transitional. I don't believe you'll have a repeat of Digg moderators being paid to promote stories. You can (and people do) pay celebrities to retweet things but that still only goes to their followers. They have to consider their brands and building and keeping their respective audiences too.
Those thinking Twitter should have an open firehose (or close to it) are neglecting the reality that Twitter is a business and needs to make money somehow. Open access to their content greatly diminishes that.
Lastly, quite a few people will speak of "betrayed" by Twitter over API access. They also believe that developers were largely responsible for making Twitter popular. As I said (just yesterday) that this is inevitable. Become too successful and the platform subsumes you into their core offering (no one wants core features controlled by third parties). Developers were I believe largely incidental to Twitter's success. Twitter succeeded (as it were) because people used it. To take credit for that as a developer community is like saying that the automobile succeeded because of car wash stations and autoshops selling rims.
EDIT: one last point. It's popular, particularly on HN, to simply build an audience or something that scales without concern for monetization. I certainly understand the logic behind this. Sometimes it works but sometimes it doesn't.
Twitter hasn't come up with a scalable business model yet because there isn't one. As much as founders can be praised for "swinging for the fences" and going all in, sometimes the best outcome is to be acquired because what you've developed isn't a viable independent business but could be an incredibly valuable part of a wider portfolio of products.
- lazylland 14y ago"Twitter succeeded (as it were) because people used it", and they did because the Twitter API is basically the "Hello World" of using a web service ! This meant ANY platform where a developer cared to bring out a Twitter client had it, and hence more people could jump in quickly. Secondly, really creative users made Twitter what it is today with Retweets and Hashtags. Twitter would be wise to not start an evaporative cooling effect.
- dasil003 14y ago> Twitter would be wise to not start an evaporative cooling effect. I think this comment is at least a couple years too late.
- cynicalkane 14y agoAside on SMS: Armchair economists like to discuss SMS as an example of oligopolies gone bad, but that doesn't pass the smell test. Telephone competition is suboptimal but SMS is uniquely bad in its outcomes; they've done a much better job on all other forms of data. Furthermore, costs vary from place to place but by all accounts SMS is still very expensive worldwide. Well, it happens that SMS is a technical hack; the data payloads are snuck into the control channel. The bandwidth in this channel is very scarce. The message could be re-routed over the data network, but the cross-carrier costs are still expensive because the receiving phone might have to use the old implemnetation.
- revelation 14y agoThats obviously a no-starter. Its not expensive because its "snuck into the control channel", which is only partially true. If that was the case and it would be immensely expensive to transport data that way, there would be a technical solution in no time. Remember that before SMS, most payload was sounds, voice communication. Even with codecs that is still much more bandwidth intensive. And don't even get started with routing voice cross-carrier with minimal latency; atleast with SMS you can still temporarily hold them while you wait for capacity to free up.