Deprecated: Assigning the return value of new by reference is deprecated in /homepages/2/d178525413/htdocs/electronic/wp-settings.php on line 512

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/2/d178525413/htdocs/electronic/wp-settings.php on line 527

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/2/d178525413/htdocs/electronic/wp-settings.php on line 534

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/2/d178525413/htdocs/electronic/wp-settings.php on line 570

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/2/d178525413/htdocs/electronic/wp-includes/wp-db.php on line 306

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/2/d178525413/htdocs/electronic/wp-includes/cache.php on line 103

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/2/d178525413/htdocs/electronic/wp-includes/cache.php on line 431

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/2/d178525413/htdocs/electronic/wp-includes/query.php on line 61

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/2/d178525413/htdocs/electronic/wp-includes/theme.php on line 1109

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/2/d178525413/htdocs/electronic/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /homepages/2/d178525413/htdocs/electronic/wp-includes/http.php on line 61
Lifestreaming by numbers < life under electronic conditions
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/kses.php on line 1003

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/functions.php on line 55

Lifestreaming by numbers


Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/link-template.php on line 107

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/link-template.php on line 132

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/link-template.php on line 107

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/link-template.php on line 132

Lifestreaming and microblogging - both tend to overlap as most lifestream services allow for short status messages and most microblogs or activity streams allow feeding RSS feeds into them - are becoming more and more common in the social web. Some argue that Twitter is increasingly being challenged by other services like Friendfeed, Plurk or identi.ca. Do the numbers reflect this? Let’s take a closer look.

First, I took Alexa’s numbers for the webpages’ reach (see here). Because the yesterday values were not available for every webpage, I took the weekly average. I calculated the relative values for each lifestreaming service and got the following picture:

Twitter’s strong position should be evident. I found it quite interesting that SocialMedian achieved such a strong position, coming up directly after FriendFeed and Plurk. But of course the numbers being so small, they are clearly not reliable. This holds for all numbers in this post. Lifestreaming may spread, but it is not used by enough internet users to allow for reliable measurement. And the numbers for active users don’t seem to be available for the services. It would be interesting to compare them as well.

The values from Google Trends for websites show a quite similar picture (see here):

Twitter has the most traffic while FriendFeed and Plurk are not very far apart. The other lifestream services are only marginally important. For Jaiku there are no numbers because it is a Google service.

Finally, I compared those two charts with the values obtained by Quantcast (see here):

Here, Twitter has the largest share while Plurk is very weak, compared with the Alexa and Google numbers.

All in all, the fail whale nonwithstanding, Twitter still seems to be the number one service when it comes to streaming your life to the internet.

But with major social networks like Facebook or Xing offering the same features, there could be new competitors for Twitter, FriendFeed and Plurk. But this competition does not express itself in traffic numbers, so this will be quite a challenge for social media measurement.

Share this post:
  • Digg
  • del.icio.us
  • Facebook
  • Google
  • Furl
  • Ma.gnolia
  • MisterWong
  • NewsVine
  • TwitThis
  • Yigg
  • Pownce
  • Reddit
  • Slashdot
  • StumbleUpon
  • Wikio
  • LinkedIn
  • Spurl