According to the application's description, Nokia Situations is able to "sense" things like the time of day, your location, what networks you're connected to, and then adjust one or more phone settings accordingly.

Then you can tell the phone what you want it to do when a particular situation occurs. This can include silencing the ringer or changing the ringtone, answering missed calls via an automatic SMS, turning on or off Bluetooth, changing the theme or wallpaper, automatically opening an app or changing the device mode.

Earlier this year, we reported on a similar technology for N97 devices called "Nokia Bots," that did much of the same thing as Situations does now. The new app, however, works on a wide range of Nokia devices, including the N97/97 mini, Symbian 3 devices, S60 (3rd Ed., Feature Pack 2), Nokia C6-00, Nokia 5228, Nokia 5230, Nokia 5230 Nuron, Nokia 5235 Comes With Music Edition, Nokia 5250, Nokia 5530 XpressMusic, Nokia 5800 XpressMusic and Nokia X6-00 phones.

In recent weeks, I've been experimenting with some newly released curation platforms. The first, Curated.by, lets you capture tweets around a specific topic using a plug-in that's installed on your Twitter.com profile. You can then easily tag and sort tweets into "bundles," which can then be embedded in a blog post for some additional context to whatever you're reporting on.

This week, I discovered startup Storify while watching the TechCrunch Disrupt conference. While Curated.by and Storify share the same core theme of curating social content, Storify goes beyond tweets by letting you insert content from YouTube, Flickr, Google search and more into "stories" which can be embedded into a Web page. I'm a sucker for experiments, so today I created something using Storify's platform. It all got kicked off with a single tweet.

From there, I took to Storify and began adding responses from the community. (Note to Storify: include Twitter mentions in addition to search in your next update).

Based on the responses, I added additional contextual information that included recent ReadWriteWeb articles and content from the various sources Storify supports. Here is the end result:

For a brand new service still in private beta, Storify is impressive. The ease of inserting tweets and additional content from across the Web was a generally pleasing experience. I did have some issues, though. After I had initially saved and embedded my story in this post, the tweets and contextual content I added randomly re-arranged. Considering the length of the story, it was a pain to have to go back and work on it for an additional 30 minutes. In terms of the presentation quality of the embed, it's good, but could use a little more beautification.

Storify lets you notify the Twitter users that were part of your story.

My biggest wish is that Storify make their stories "live." By that, I mean that I want anyone to be able to leave a comment on something that has been added to a story. For example, as you can see I replied to several of the tweets in the story using Storify's text module. But since there is no way for someone to reply to those, the conversation halts. I'm not sure if Storify wants their product to be that interactive, but it's something to consider, at least as an option.

I'm happy startups are starting to tackle curation. For a community manager, it's very nice to be able to capture what your audience is talking about and build an experience around it. It remains to be seen if Storify can make it as a standalone service, but I'd love to see their tools end up in a content management system like Movable Type and Wordpress.

What are your thoughts on Storify and emerging curation tools? Let us know in the comments!

Since the launch of the contextual link advertising product on ReadWriteWeb, we at Hakia have been anxious to see the results and evaluate the success of our contextual advertising product, Contexa. The Contexa system matches the semantic context of a blog post with a sponsor's criteria on the fly to deliver relevant ads to the reader. Participating ReadWriteWeb sponsors have provided the contextual engine with up to three "trigger phrases" that define their business. As a reader of the blog, you may have seen the product's implementation at the bottom of certain blog entries, as shown below. You can see another example here.

As we began this exciting journey, the ReadWriteWeb team defined its objective as follows:

1. "To offer value to our readers by providing advertising links in the context of what they are reading, links that would therefore more likely be of interest to them, and
2. To offer a higher level of engagement to our advertisers, resulting in both more branding impressions and more click-throughs."

The preliminary aggregated statistics of the six participating sponsors (excluding Hakia), covering a 40-day period, demonstrate that the Contexa system has met ReadWriteWeb's objectives:

• The Contexa system increased ad clicks by 14% (i.e. advertiser received, on average, 14% more ad clicks).
• The click-through rate (CTR) for Contexa was more than twice that of ReadWriteWeb's 125 x 125 banner ads.

We decided to turn the tables and interview Bernard Lunn, ReadWriteWeb's COO and Feature Writer for his feedback! Hakia's own COO, Melek Pulatkonak, poses the questions.

Melek: Bernard, we have been working together on the ReadWriteWeb contextual link advertising system for a while. Has the system met your expectations?

Bernard: Yes, it has. We wanted to see if it would generate a meaningful uplift in CTR, and it has.

Melek: What feedback have you received from advertisers? And what would you recommend to participating advertisers going forward?

Bernard: Advertisers have to get the traffic–relevance balance right. You can drive a lot of clicks with a hot term - something we are writing about a lot - but if the relevance is low, the advertiser won't get good conversions. As with any new type of advertising, an art and science emerges over time. People know how to buy search terms on Google, but this is a bit different. I think we need to get better at creating more of a feedback loop (e.g. stats on how different terms have performed) so that advertisers can tune their keyword selection accordingly. Each advertiser has different needs and knows its market intimately, so it is best positioned to decide what works and how to tune its selection.

Melek: What's next? What is your vision?

Bernard: For this first phase, we provided Contexa to our long-term sponsors. In the next phase, we want to offer Contexa as a standalone offering, so that advertisers can purchase keywords (or trigger phrases) directly on ReadWriteWeb. This will be an entry-level self-service advertising option that many smaller startups have requested.

Melek: Anything else you would like to add?

Bernard: Context matters to engagement. That is an obvious statement, but doing it right has been hard, and the opportunities for bloggers to offer ads that engage readers well and offer them value have been limited. Contexa is a good step in this important journey.

We thank the ReadWriteWeb team for working with us closely to create a new contextual ad system for blogs and other publishers. To learn more about Contexa, please contact us at bdev@hakia.com.

Barnes says his new service Panels.net gets reader engagement numbers above 10% - an astonishing number in advertising. He says that's because his Panels are genuinely useful. At first blush they strike us as a little awkward but the potential here is big. Well selected, up-to-the-minute info about any link we see online sounds like a great idea - if it works.

Panels.net requires one line of Javascript to be added to web pages. The service then ads a little icon to any link that goes to an "entity" - like a person or business. The links can be styled to your liking as a publisher, and when hovered over they produce a pop up "panel."

There's a site: search function for any domain in its panel, there's info pulled in from the Crunchbase database, there's a lot of information available in these little panels.

The variety of information is quite diverse and Barnes says what's served up is customized depending on what kind of entity you're looking at. You can see Panels in action over on Barnes' personal blog; the service will be rolled out to bloggers over the coming months.

Serious Technology

This isn't a fly-by-night organization deciding to throw a handful of RSS feeds into a Javascript pop-up either. Craig Barnes is a four time CEO who started then sold for $140 million what's now one of the top handful of font management software companies in the world, Extensis, in 2001. He then served as the CEO for venture backed enterprise RSS company Attensa. Now he's out on his own, making hires and getting ready to launch a service for which neither the market nor the storage and delivery technology was prepared when he thought of it years ago.

Is it Unobtrusive?

As many of us found out with the recent launch of Google SearchWiki, adding symbols to a familiar, simple web page can be very disruptive. Ostensible Panels competitor Snap has faced years of criticism for their over-eager pop-ups.

We're not sure how Panels scores on obtrusiveness. Its popups are polite and relatively attractive, but the icons you have to click on to launch them are a little hard to swallow. It's a very fine line for services like this between being invisible and being used. We don't know what the solution is, but we do know it's a big issue.

Is it Truly Useful?

Fortunately the usefulness is immediately apparent when you look at a Panels popup. If you're interested in an organization's web traffic, financial trends, recent mentions in the press - and many of us are - then for many links Panels will serve you well.

Is it Up to Date and Well Populated?

Barnes says that a signifigant amount of thought has been put into caching much of the information served up through Panels. That's smart and we hope it will make a big difference. When we tested the panels they were sometimes a little slow to respond and many of the display options just said "coming soon." We would need to see this resolved before we were to, for example, put Panels on our site.

Is It Intelligently Delivered?

There are some decisions that can be presumed in the user experience here that don't appear to be now. We need clicks to be kept to a minimum. If, for example, we've clicked on 3 Panels icons on a page and navigated to the website traffic numbers first for each of them - then we'd like to have the panel pop up and go immediately to the website traffic view. (Update: On second look, it appears this is done to some degree, at least the first level of navigation is repeated in subsequent Panels.)

The point is that the user experience needs to be as smooth as turning a box of cereal around to look right at its nutritional panel. Right now the user experience doesn't quite feel that easy.

It's early days, but we hope the company is prioritizing user experience. We suspect that forthcoming improvements in browser handling of Javascript will also help make Panels smoother to use.

Long Range Outlook

Panels is a very good idea. If it can be executed upon well, and overcome the kinds of obstacles listed above, then we think this just-launched startup has as good a chance as any. We want it to work better than it does today, but we're sure it will.

Key information available about people and companies online could soon be at our fingertips at a moment's notice as we browse the web. That really is how it ought to be.