{"id":34437,"date":"2009-10-28T15:00:27","date_gmt":"2009-10-28T19:00:27","guid":{"rendered":"http:\/\/gigaom.com\/?p=77293"},"modified":"2009-10-28T15:00:27","modified_gmt":"2009-10-28T19:00:27","slug":"what-if-microsoft-had-developed-twitter-continued","status":"publish","type":"post","link":"https:\/\/mereja.media\/index\/34437","title":{"rendered":"What If Microsoft Had Developed Twitter? (Continued)"},"content":{"rendered":"
\n

\"\"I got several good laughs out of Tsahi Levent-Levi’s speculative post “What If Microsoft Developed Twitter?<\/a>” In it, he conjures up a Redmond-enhanced version of the microblogging platform that would look and work a little, er, differently from the one we’re using now. “You would have to sign a EULA for each tweet you send out,” he imagines. “You would have to reset your Twitter client every day,” he adds, and “you would have to get used to the blue tweet of death.” Here are four more attributes that we might expect from a Microsoft version of Twitter.<\/p>\n

An unabridged eBook version of “War and Peace” would pop up as you load the\u00a0 necessary software libraries and security patches in preparation for your first tweet of the day:<\/p>\n\n\n\n
\"\"<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

You would have the terms “Cancer” and “Hippie GPL Rubbish<\/a>” emblazoned as watermarks on any tweet you send out on the topic of open source software:<\/p>\n\n\n\n
\"\"<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

As daily software updates arrived, you would have two, and only two options: “Install” and “Remind Me Later:”<\/p>\n\n\n\n
\"\"<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Any attempts to use words such as “bang” or “bong” in tweets would be replaced with Bing:<\/p>\n\n\n\n
\"\"<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

What other enhancements would Microsoft’s version of Twitter have?<\/p>\n

\"\"<\/div>\n

\n

<\/a><\/p>\n