This post is the third segment in my series on an architecture for the social web. Previously: How social networks can replace email, which is a non-technical approach to the issues, and my follow-up describing how to build a social web architecture using available technology today. So what about direct messaging? In my previous post, I described content notifications in the social web as being Activity Streams updates in response to requests signed with an OAuth key. Each individual contact w
My previous post was a response to Gartner’s prediction last month that social networking would replace email as the “primary vehicle for interpersonal communications for 20 percent of business users.” In it, I named some properties that would need to be held by any social networking system that would successfully replace email. * Ease of use * Ubiquity across devices * Platform, service and infrastructure independence My argument boiled down to the following statement: Email has succeeded
The analysis firm Gartner just released five key predictions for social software: 1. By 2014, social networking services will replace e-mail as the primary vehicle for interpersonal communications for 20 percent of business users. 2. By 2012, over 50 percent of enterprises will use activity streams that include microblogging, but stand-alone enterprise microblogging will have less than 5 percent penetration. 3. Through 2012, over 70 percent of IT-dominated social media initiatives will fail.