Good news everyone. We now support 2 new platforms: Identi.ca and Propeller.

Identi.ca

Twitter is growing faster than weed and you probably know that by looking at every graph on uberVU. But there are other services out there and we are doing the best we can to support them all. identi.ca is one of them. We like identi.ca because it’s more open than Twitter and it’s based on open-source software –  StatusNet (formerly Laconica).

Propeller

Netscape may not be one of the hottest destinations on the web right now, but while Calacanis was in charge, he created a cool destination Digg-like website. Now known as Propeller, the website is still a cool destination with a nice following, and it is our pleasure to add it as a data-source for ContextVoice.

Please refer to the updated documentation. The new generators are identica and propeller.

As the new platforms are rolling you will see  new sources in uberVU too.

You can now filter results from the uberVU conversational engine based on language. We noticed getting results from all over the globe can become quite chaotic so language detection was a must.

uberVU is now smart enough to understand:

• arabic
• bulgarian
• chinese
• danish
• dutch
• english
• persian
• finnish
• french
• german
• hungarian
• icelandic
• italian
• japanese
• korean
• norwegian
• polish
• portuguese
• romanian
• russian
• serbian
• spanish
• swedish
• thai
• turkish
• ukrainian

This brings a new level of refinement to the Context Voice API and you can now use it for localized search results. We are looking fwd to see what you can build.

Read the full documentation.

Today is party time at ContextVoice / uberVU as we’re officialy launching our Search API as part of the ContextVoice suite of APIs.

Why another Search API? Don’t we have blog search and Twitter search already?

Yes, we do. But we do something completely different. We do conversational search. A conversation is usually a story (blog post, news article) and all its related comments from all over the Web. So a blog post that has comments on Digg, has been retweeted by people and has got comments on FriendFeed is, for us, a single conversation.

Blog search only indexes blog posts and leaves out comments of any kind. And it’s usually slow.

Twitter indexes only tweets that contain the keyword you’re searching for. It’s close to real-time.

We index both the story content and all the distributed comment content and we return as a result complete conversations. And we’re close to real-time. The best of both worlds.

And this is useful because…?

The Web right now is all about conversations. However, until now, search engines have mostly returned results by relevance (Google), recency (Twitter) or some sort of combination (blog search). But out of those recent results, which one is more important? Where’s all the attention? What’s hot right now as opposed to what’s just fresh?

What’s very important to know is what Conversations (not blog posts) are HOT right now – so you can participate and make decisions in close to real-time. That’s what our API is focusing on.

What to expect from our search

Full conversation search. Because we don’t index just page content but all the reactions and comments from all over the web our results offer a better understanding of the conversation than a regular blog search. The blog post may be about the Google OS, but the comments are mostly about Microsoft. Our Search makes that visible to you.

Close To Real-Time results. We monitor the top social media sites in realtime so if something happens there, you know instantly.

Filtering options. We can show you the most relevant, the newest or the hottest conversations. We calculate the hotness based on conversation acceleration – how many reactions it got in the last time-frame. So a conversation with 10 reactions in the last minute may be hotter than one with 1500 reactions distributed over a month. But the hot conversation matters more, because that’s the one that has the attention and momentum.

What to build with the API

The Search we provide can be used in a lot of products and dashboards. uberVU.com, for example, is entirely built on top of this API. You should check it out as it’s a great starting point for what’s possible with the Search API.

Social media dashboards – want to search entire conversations for your brand of product and get an insight into what’s hot right now and where the attention is – whether on Twitter, FriendFeed or blogs? The Search API is a great place to start

Memetrackers – interested in building a meme site for the NFL or the latest gadgets? Just use the Search API and get the hottest conversations about that topic in close to real-time.

Community management projects – want to bring fresh content and community conversations from all over the Web to your site or community? Search for the topics you’re interested in with our Search API and expose the hottest conversations on your site. We don’t just get the stories, we get the comments. And the comments are the most important part of a community. People comment if other people have commented. That’s what you want.

Financial analytics – search for your favorite company and graph comments to the evolution of the stock quote. You may be intrigued at what you find.

These are just some starting ideas, I’m sure there’s a lot more you can think of.

Exciting news everybody. There is a new call parameter threaded=true that returns a threaded conversation. It works for all of our supported platforms. So if someone replies to another comment on Digg it will appear the same in Context Voice. Retwitts are treated as children of the original twitt.

Today we also introduce Yahoo Buzz as a new supported platform. It was available for some days but we announce it officially today. And we now get updates from FriendFeed in real-time…. as the rest of the platforms.

We look forward for your input.

We are moving some data around so the system will be down for 3 hours. We will be back around 2 PM GMT. Sorry for the inconvenience.

Later edit: Done

We had the pleasure to meet the Traveling Geeks in London today. It was super-cool to meet people like Robert Scoble,  Craig Newmark, Howard Rheingold, Meghan Asha, JD Lasica, Susan Bratton, Jeff Saperstein, Renee Blodgett, Jim “Sky” Schuyler, Ayelet Noff and to get their thoughts on what we are building. Awesome Seecamp event.

It was a very unusual networking event because we had a 3-minute pitch for the geeks to get an idea on what we are doing and then talk to each of them for 9 minutes. If you are thinking of speed dating you are right. That was exactly how it was. In our pitch we decided to talk on why building the social graph is important. Main takeaways:

• We are talking about conversations for more than 10 years now but all that we have is millions of unrelated messages, with no context that you can not do anything interesting with them.
• Context Voice brings order to all the chaos by creating a search-able index of platform agnostic conversations that you can track in real time.
• This is very important because we help people find and interact with their tribe.
• You can do all sort of amazing stuff on top of all the data we are giving you.

Robert also did a nice live interview with us that we embedded bellow:

Related articles by Zemanta

• Traveling Geeks are Coming to London (blogs.msdn.com)
• Traveling Geeks Are Going to London! (blonde2dot0.com)
• Traveling Geeks Are Going to London! (thenextweb.com)
• Coming Soon: Even More TechCrunch in London (techcrunch.com)
• Introducing Traveling Geeks London (socialmedia.biz)

We made some updates to our pricing/usage scheme today:

• Commercial use for the free version
  Our thinking was that if people make money out of the API it would be nice to get a share of that. What we didn’t take into consideration was that you can still start a commercial project and not make any money for some time.  Not to mention that many of the applications that people thought of building with the API were commercial apps. So from now on you can use the free version for all your business projects too.
• Number of API calls
  We still have the 5000 calls/day limit. However if you are working on a cool project and need more than 5000 calls give us an email/ reach us on Twitter etc, tell us about it and we would be more than happy to increase that limit to help your app grow.

Have fun and enjoy the summer!

Related articles by Zemanta

• The Social Data Player Platform is Now Commercially Available – Embed Datasets in Your Website (socrata.com)
• Twitter Increases API Limit (mashable.com)

Tweetvisor is one of the users of ContextVoice API. Today we asked Nelu, the developer of Tweetvisor, a few questions about his product, Context Voice and live in general.

Who are you and what do you do for a living?

I am Nelu Lazar, a Romanian living in the US. During regular business hours I am an Electrical Project Engineer, leading remotely an off-shore Romanian team in Brasov to design high performance electronic equipment for large off-highway trucks, locomotives, power generators. Evenings and nights I am a dad of two, a husband, an entrepreneur, a web developer and a social media and networking enthusiast. Traveler, soccer player, musician, biker and more, the rest of the time.

What is Tweetvisor?

Tweetvisor slightly deviated from its original purpose, shaping now more as a web-based interface that extends Twitter’s meaning. It basically is a fully-featured Ajax-powered Twitter client running in The Cloud. Some of its features:

• Manage multiple accounts (personal, corporate etc.)
• Multi-column templates, with auto-refresh (replies, DMs, hot-topic and various timelines)
• Tabbed browsing (each user, trend, hashtag, stock ticker etc. has its own tab)
• Display conversation threads (to better understand friends’ tweets)
• Groups and user Tags (for categorizing your friends)
• Save favorite search topics
• Complex searches, geolocation search, with option to save search query for later use
• Youtube, Vimeo and Metacafe inline thumbs
• TwitPic and Pikchur inline photo previews
• Picture uploads via TwitPic
• Stock tickers links
• Hashtag links
• Mouseover replies opens “in reply to” tweet
• Live Twitter trends list
• Manage followers
• Favorite tweets list
• Inline video replies

How did you find about ContextVoice?

Even though I live far away from my country, I am watching very closely everything that is happening in Romanian online space. I’ve started light personal web projects since late ’90s, when “Transylvania” University’s leda.unitbv.ro and zzn.com hosting service were some accessible tools to play with HTML, but I am more involved in Romanian networking since 2006 when blogs and other social web tools began to be embraced in Romania as well. So this way I’ve initially heard about uberVU and its ascendant path to becoming a very good tool that builds the conversational graph around web comments, reactions and mentions world wide. Recently there was a discussion opened with uberVU and ContextVoice’s founder Vladimir Oane about integrating their API into Tweetvisor’s tweets timelines and the feed reader.

What do you use the ContextVoice API for?

Tweetvisor - Context Voice integration

Thousands of links are being shared every day on Twitter. There is definitely a lot of noise out there, but you’d still like to find out the latest good news and articles, or what people are talking about your brand, company or your blog articles. As a solution to this trend, Tweetvisor is now displaying world wide reactions to any URL shared on Twitter and listed with the web-based application, via newly launched ContextVoice service. Tweetvisor’s integrated Feed Reader also displays ContextVoice’s world wide reactions for every blog posts.

What do you find most exciting about ContextVoice?

ContextVoice makes a very easy task out of tracking comments and reactions for any article URL across the Internet. You can see how your links or keywords are shared, propagated and commented on many web platforms. ContextVoice API is a good tool for personal research, but it is an even powerful tool for brands, companies and organizations that really needs to keep a close eye on what their customers have to say about their business activity or, say, newly launched products.

Is there something we must do to make you happier?

I’ve just implemented the API, and ContextVoice is doing a very good job on Tweetvisor, the integration performs smoothly. There will be a monitoring timeframe for the next few weeks, to observe how Twitter users are following world wide conversations for URLs shared on every tweets. For the near future I am opened to increasing implementation’s capabilities by adding more features that will help people track web reactions they’re interested in.

Final words?

I am very happy ContextVoice and Tweetvisor managed to cooperate very well to accomplish this integration. We both hope people will find these tools helpful for their daily-basis tweeting needs.

Related articles by Zemanta

• Introducing Context Voice (contextvoice.com)
• uberVU brands its API as ContextVoice – launches a free and a paid service (thenextweb.com)
• 7 interesting Twitter tools (en.onsoftware.com)

lett

Last week was totally hectic. We launched a new website, a new product and a new version of the API.  So we would like to thank all the people who helped us to get things out the door:

Brohouse for the amazing logo

We needed a new logo for Context Voice and we needed it fast. So Brohouse was there to help us create a logo in almost no-time. You can read the whole story on their blog. Thanks again guys!

Steve Ho for helping us solve some crazy database issues

A month ago we ran into some very weird problems with our databases. Steve was calm enough to help us methodically test all the possible causes and help us identify the problem(s) and solve them. Thank you Steve! We owe you one!

All the great people who wrote about our launch

I am thinking of:

• FocusIT for letting our fellow Romanian hackers know about the change
• OpenCoffee Bucharest for hosting the first ContextVoice presentation
• Stefano Bernardi for breaking the news before everyone else on thestartup.eu
• Dana Oshiro for her great article and interview in ReadWriteWeb
• Mircea Goia for the great article in TheNextWeb
• Seedcamp for mentioning our launch on their blog and breaking the news to all the European startups.

Thank you ALL!

Related articles by Zemanta

• Introducing 2 New Writers: Steven Walling and Dana Oshiro (readwriteweb.com)
• Context Voice at Open Coffee (contextvoice.com)

I read a few blog posts lately about where the Web is going and they struck a cord. They managed to articulate more clearly some of the things that we felt intuitively when we started building ContextVoice / uberVU and were not able to clearly express.

It’s going to be a pretty long article, so you can skip to the short version/conclusion here.

Streams

The Web is definitely moving towards a stream-like, conversational structure. Twitter, Facebook, FriendFeed, all of these work as streams. More importantly, to emphasize the trend, feed readers and even Gmail are starting to look like streams/conversations. I find myself spending over 50% of my personal time online in a stream environment and, if you consider Gmail a stream-like experience, probably close to 80% of my work time inside streams.

There are two approaches to streams that, if you look at how we function as human beings in real life, are totally complementary.

Imagine meeting a friend outside a coffee shop en route to a meeting. The friend, with the context around her is an atom in a stream of inputs that demands your attention. You start talking to her about something, the conversation then suddenly focuses on something else. Your phone rings and so you focus your attention on the phone call, which is actually just another atom in the stream. Your meeting partner is going to be late. You then switch your attention to your friend and start talking about something completely different.

This is the way we operate in real life when we try to find information or socialize, yet the Web does not reflect that. Until now.

I’d associate the stream of information all around you with the way Twitter works, while the way we dig deeper into a certain subject / interact with a social object is more like FriendFeed works – or ContextVoice / uberVU for that matter.

Whatever the type of stream you experience, soon enough you realize you cannot consume it all, as it was not conceived for that. Navigation becomes more important that it has been so far with pages, because a stream changes continuously. It’s not just about finding some “relevant” information, like you do on Google, because that may not be relevant anymore in a changing stream. I’d argue that it’s not even just about finding “real time” information, like you do on Twitter search, because that only addresses the time axis. It’s a combination of the two that probably yields the best results.

How we think about streams

We started tracking comments from all over the Web around URLs because we felt a conversation does not stay trapped within a single site or domain and so you should not experience the conversation that way. The conversation flows between blogs, Twitter, FriendFeed and social networks but it’s essentially the same conversations.

Pages don’t matter anymore, it’s all about being able to tap into the right stream at the right time and filter it as you like.

What ContextVoice does is find related bits of streams (trackbacks, comments, tweets) from the larger stream, sticks them together and creates a new stream that we keep track of. We think it’s one way of navigating the larger Stream, by sticking together related pieces that are part of the same conversation.

As streams will be the fabric of the Web, being able to tap into streams to extract valuable information is going to be key. Navigating and participating in streams will be part of most web apps and will be used by both people and businesses. Everybody will be using this technology, just like e-mail and RSS. It’s already happening, with buzztracking tools and customer service on Twitter.

We can easily imagine applications tapping into streams to extract events, financial and health information, interests, relationships and a lot of other types of data, processing it and then pushing back to the Stream, to be consumed. This is where ContextVoice comes in providing applications with easily accessible ways of tapping the Stream.

Taking this to the next level, we believe search is probably going to still be the preferred way of finding information in the Stream. But I think of search not as it is today, but mostly as a combination of Tracking and Discovery. You’ll express what you want to know about, not necessarily now, but perpetually, and search system should be smart enough to pick up the appropriate pieces of the Stream, apply filters and deliver the right data to you, as a stream.

This is the approach we’re taking with uberVU. uberVU will be a search and analytics product, where you’ll be able to both search for conversations around URLs and search for keywords. The results returned will be whole conversations, not just posts or tweets containing the keyword. And, of course, you’ll be able to experience searching for a keyword as a stream of conversations updated in close to realtime.

We think this is an important distinction which ties into the role Context will play in the new Web.

The Role of Context

The Stream is made up of atomic pieces that constantly flow, with not much context to go by. Think of your Twitter stream – continuous updates on different subjects, shared links – each update does not have much context except the author and the time of posting.

People’s need for context became evident even on Twitter. That’s why we have @, RT or #. These symbols are trying to bring in a piece of context and encapsulate it in the atomic bit of information. So context is needed if we are to make sense of what information in the Stream means and where our attention should lie.

A more subtle implication of this fact is that context should be able to be incapsulated in the information itself and easily travel with the information wherever it goes. Of course, context changes over time and a piece of information can be looked at from within different contexts.

This is exactly why we built ContextVoice as a different product than uberVU.

Firstly, ContextVoice gets CONTEXT around stories from all over the Web. Instead of getting simple bits of information with no context around them, we get comments from all over the Web that are about the same story. This makes for some interesting information. You can see actual comments but also how they’re related to each other (RT, threads, comments to trackbacks), how they happened on the timeline, how fast the conversation has accelerated and decelerated, etc.

Secondly, as I said before, CONTEXT should be able to travel with the data. This can prove really tricky, as some conversations are made up of over 10,000 bits of information. In order to solve this problem, ContextVoice can return all the CONTEXT around a story in a single API call. We can’t encapsulate it in the data, as it’s not practical, but we have set it free and easily accessible.

Thirdly, we are not the only ones that will need this data. A lot of companies will use it, as we move more and more towards a more streamy Web. What we’re doing with uberVU is a single use case in a sea of possibilities.

Context can be used for many things. More context is usually better, but after a certain limit, I think context will only be useful in realtime search. People won’t be able to process it, but we’ll need it if we want to get relevant search results in realtime. As uberVU will mostly be a search product, we’re trying to get as much context around stories as we can, there no such thing as too much.

In Short

The Web is turning into a realtime Stream. We won’t be able to digest it all, so navigation will be increasingly important. One way to navigate the Stream will be through Search, but smart realtime search needs a lot of Context around the atomic bits of information if we are to find the truly relevant information we need from this everflowing, noisy Stream.

We built ContextVoice in order to get Context around stories from all over the Web. We get comments, mentions, reactions, tweets and other things, some of them in close to real time. ContextVoice is an API because of two reasons:

1. Context should be able to travel with the data. As we can’t encapsulate this much context within the data itself, providing it as an API call seems to be the easiest way.

2. As the Stream becomes the very fabric of the Web, being able to tap it will probably become like RSS or e-mail. Everyone will need this technology as part of their apps or businesses.

uberVU, the product that uses ContextVoice will try to tackle one of the problems of navigating this Stream – what you’d call Search and I’d call Track/Discovery. Finding fully contextual conversations (streams) to participate in, not just atomic bits that contain keywords.

Back to top

It’s been a long article, but if you’ve come this far, I encourage you to hang in there for a couple more seconds and share your thoughts.