21 Mar 2008

MicroPulse thoughts

I had several thoughts when reading Martin’s MicroPulse proposal. It was not easy to get my head around it. I am not sure whether it is appropriate to respond on my blog, but here I go. The thoughts are a bit unstructured and low-level at this stage and are created while reading.

I am a bit reluctant in creating systems. There are already so many things around. But then I am not familiar enough with KnowledgePulse.

The concept of ‘Continuous Partial Attention’ is interesting. With all the information flowing towards our devices (thanks to RSS), we live in an information sea that is very close to us. The question is whether we will pay attention to that sea. If I look at Twitter or Jaiku, then there is a peripheral component. But there are also other examples reminding of radio.

On my platform I created such a sea. Thanks to Growl a small windowlet pops up in the right-top corner of my screen, with the latest tweet. This windowlet stays there for 1 second and dissolves into the background. I have a choice to look at it and read the message, or just let it pass. Information in this windowlet can come from a variety of sources, such as Twitter, Jaiku, last.fm and all kinds of other status messages from local applications. Think also of instant messaging clients, where you notice your friends login and -out. This kind of information flow is like being ‘next to the sea’.

Fortunately there is no attention grabbing. When I do not look at this local sea, then it will be lost, but nothing will be lost.

This is a bit different from beeps from the mail application to indicate that there is new mail, or indicators to show how much new mail, rss-item, etc you have waiting for you.

The idea of an application taking over when there is no foreground activity (afk), reminds me of a screensaver. This screensaver would then sequentially present new Items from the subscribed RSS feeds.

The Growl-messages could be ‘calls for attention’. It however depends how intrusive these calls are. At the moment it is relatively hard for me to react to these calls: I can not click on them, I have to see the associated application and put that application to the front.

As soon as you are going to react to impulses from the sea, you are going in. You are opeining your Twitter client, RSS-client, etc, and are going to read the information for real.

In the MicroPulse description also more intrusive examples of Micropulses are mentioned. I have to ‘click-away’ these pulses, the come back until I did something with it. It reminds me of annoying pop-up, pop-under windows, of bouncing dock-items, etc. All requiring me to change my focus from my current task to something else. I do not want to be overwhelmed by waves from the sea.

The micro-information loop tries to establish the relation between this sea and the user. This relation is determined by the interaction the user has with that information, i.e. the amount of attention the user awards to that information. As described, there can be many levels of (’moe’ tweets whether I like to play Mario Kart with him on the DS) attention.

A question is, whether this attention recording process must be something explicit, as described with the Flash cards.

The idea of a context dependent sea/radio is an interesting one. It might lower the information overload burden, it is no longer necessary to switch contexts. But then these tweets ‘out of context’ are also nice and offer the coffe machine environment.

I have mixed feelings on the recorder thing. I am all in favor, in fact I tried to set up something for my self with, blogs, bookmarks, etc. In reality I do not seem to benefit from it. I guess that this is just the state of art. Recommendation is still extremely lousy. But here seems to main challenge.

For the moment no comments on the system part, it all depends what you want to accomplish.

[Inspiration MicroPulse]

Categories/tags: MicroContentgeneral
PermaLink • (2) Comments TrackBacks
Page 1 of 1 pages