[Once in a while there comes a time to write a post unrelated to VoIP. Or anything else in this blog for that matter. The sole purpose of the post is to attract readers that might find it amusing enough to stay around a bit - or god forbid subscribe to the blog in question.
Guess what? You are now reading such a post.]
What if Microsoft was the company behind the service we all call Twitter?
Every tweet would be a maximum of 140 characters, but would need to download a 2Mb message, containing various XML markups and a ton of security.
You know – you would be able to change the font of your tweet. And the size of it. And the color. Set it to bold. Or italicize it. That kind of tweaking takes space.
Add to that encryption for privacy concerns, authentication, server signatures, etc.
You would be readying yourself for Twitter 2010
And just when you got used to the way twitter handles them RT messages.
Oh, and it will require Silverlight, .NET, ActiveX, and Internet Explorer 9 to read, of course.
They would have come up with a new SDK technology once a year
Remember the fact that you’re getting ready for Twitter 2010? So if you are a developer, that change in retweets might change the application you’ve written for twitter.
You would have to sign an EULA for each tweet you send out
You know, saying that the tweet you send is up to you, no one else is responsible for it, even if it kills your machine, or the machine of the people receiving it.
And one for each tweet you want to read, of course.
Oh – what’s that you say? Twitter just changed their terms of service?
You would have to reset your twitter client EVERY day
Some of us actually HAVE to do that, since their twitter clients gobble up memory relentlessly without giving it back to the community: I used to close my tweetdeck and reopen it about twice a day a few versions back.
Image from Andy Brudtkuhl’s blog
You would have to get used to “the blue tweet of death”
Also known as a Fail Whale in some cultures.
You couldn’t use Twitter on your Mac
Or you could. Only it would be an older version of Twitter with the possibility of stopping support at any time.
You could only use Windows Media Player to view videos tweeted
While that might not be true, there has been some complaints about twitter not playing nice with open standards.
Nagging administration again…
- I’d like to thank Sagee for supplying some of the “what if” answers above.
- I originally wanted to write a post titled “What If Cisco Acquired Tandberg”, but most of the blogs out there beat me to it.
- You’re more than invited to subscribe to this blog or to our blog network if VoIP interests you.
- UPDATE: Sagee also wrote his own version – What If Twitter Developed Video Conferencing?
Oh! And if I missed some, feel free to comment below and add your own!