The Passive Web
by Patrick Ruffini :: March 24th, 2007 10:58 pmRex Hammock makes the case why no one should freak out over Twitter.
I’ll happily admit that I’m on the other side of this particular social disconnect. I get the Internet. I get blogs (or at least I think I do). But I fully understand that these are mature / tapped out media. Updating my status every fifteen minutes and/or texting my buddies is something I just don’t do. (Heck, I even hate using Google Calendar.) This makes me very self-conscious about my own early adopter credentials, seeing as I’m not even 30 yet.
I don’t do any of these things because they seem like a lot of work — for very little payoff. I don’t know if very many of the young ‘uns feel the same way or not.
To get mainstream adoption (particularly among folks my age or older), all of these status updates / social bookmarking / lifestream tools could use a layer of passivity built in. Which means I don’t have to tag, upload to Flickr, upload to Facebook, Twitter in, etc. to use them; just analyze my clickstream and inbound mail to build patterns for me. One of the concepts that intrigued me at SXSW was the idea of passively multiplayer games — comparing my activity to that of others through an objective look at clickstream data.
Just as Rex notes, there will be business applications to Twitter beyond the initial silliness we’re seeing now. When that happens, the real power behind these tools won’t be in forcing users to update their status, but building systems that will do it for them. I’ve been using Attention Trust’s clickstream data to analyze my browsing habits for a while, telling me how many hours a week I’m online, or how much time I spend doing email or reading blogs. Facebook’s news feed is another great auto-discovery tool, altering me to new groups and interesting people on the network. Auto-tagging would be great for a CRM platform; the thought is that all inbound email could be tagged based on the prevalence of statistically anomalous terms. A tag cloud could tell you what your customers are saying right now before you even read their mail. The clear benefit: it’s objective where normal tagging is editorially biased.
WordPress database error: [Can't open file: 'ocwp_comments.MYD'. (errno: 144)] WordPress database error: [Can't open file: 'ocwp_comments.MYD'. (errno: 144)] WordPress database error: [Can't open file: 'ocwp_comments.MYD'. (errno: 144)] WordPress database error: [Can't open file: 'ocwp_comments.MYD'. (errno: 144)] WordPress database error: [Can't open file: 'ocwp_comments.MYD'. (errno: 144)] WordPress database error: [Can't open file: 'ocwp_comments.MYD'. (errno: 144)]
![]()
Comments (
SELECT ID, COUNT( comment_ID ) AS ccount
FROM ocwp_posts
LEFT JOIN ocwp_comments ON ( comment_post_ID = ID AND comment_approved = '1' AND comment_type='')
WHERE post_status = 'publish' AND ID IN (47)
GROUP BY ID
SELECT ID, COUNT( comment_ID ) AS ccount
FROM ocwp_posts
LEFT JOIN ocwp_comments ON ( comment_post_ID = ID AND comment_approved = '1' AND comment_type='pingback')
WHERE post_status = 'publish' AND ID IN (47)
GROUP BY ID
SELECT ID, COUNT( comment_ID ) AS ccount
FROM ocwp_posts
LEFT JOIN ocwp_comments ON ( comment_post_ID = ID AND comment_approved = '1' AND comment_type='trackback')
WHERE post_status = 'publish' AND ID IN (47)
GROUP BY ID
Trackbacks (
SELECT ID, COUNT( comment_ID ) AS ccount
FROM ocwp_posts
LEFT JOIN ocwp_comments ON ( comment_post_ID = ID AND comment_approved = '1' AND comment_type='')
WHERE post_status = 'publish' AND ID IN (47)
GROUP BY ID
SELECT ID, COUNT( comment_ID ) AS ccount
FROM ocwp_posts
LEFT JOIN ocwp_comments ON ( comment_post_ID = ID AND comment_approved = '1' AND comment_type='pingback')
WHERE post_status = 'publish' AND ID IN (47)
GROUP BY ID
SELECT ID, COUNT( comment_ID ) AS ccount
FROM ocwp_posts
LEFT JOIN ocwp_comments ON ( comment_post_ID = ID AND comment_approved = '1' AND comment_type='trackback')
WHERE post_status = 'publish' AND ID IN (47)
GROUP BY ID
del.icio.us
digg it
subscribe
You can leave a response, or trackback from your own site.
WordPress database error: [Can't open file: 'ocwp_comments.MYD'. (errno: 144)]
SELECT * FROM ocwp_comments WHERE comment_post_ID = '47' AND comment_approved = '1' ORDER BY comment_date




















