This blog has moved to http://tomchikoore.com/
One of the questions that I am often asked is how Filtrbox is different from traditional RSS readers and aggregators. The following are the major differences:
Closed Search Domain vs. Open Search Domain
When using traditional RSS aggregators, the user supplies the list of RSS feeds. This means that the domain of information gathered by a traditional RSS reader/aggregator is limited to the RSS feeds that are known to the user. I call this a closed search domain. However, in an environment such the one we have today where thousands of new content sources are being created on a daily basis and anyone can potentially become a publisher, it is unrealistic to put the burden on the user to keep up with the thousands of new content sources that are sprouting up each day. Filtrbox takes this burdensome responsibility away from the user and discovers the new content sources for the user because Filtrbox’s search domain covers all the new content sources. I call this an open search domain. The user can also add RSS feeds to the search domain, thereby guaranteeing that their RSS feeds of interest are searched. This approach leads to the user discovering new content sources.
Publisher centric vs. Content centric
Traditional RSS readers/aggregators present to the user all the content that is published by a specific publisher regardless of whether the user is interested in the content or not. Thus, the traditional RSS readers/aggregators implement a publisher centric information consumption model. On the other hand, Filtrbox implements a content centric information consumption model. Rather than deliver to the user all the content published by a specific publisher, whether its relevant or not, Filtrbox allows the user to filter for the content that they are interested in from ANY publisher by providing contextual keywords. The content centric model implemented by Filtrbox greatly reduces information overload because each piece of content is examined and filtered for contextual relevance before it is delivered to the user.
No filtering vs. Contextual relevance filtering
As indicated above, traditional RSS aggregators do not filter the content. All content published by a publisher in the user’s closed search domain is delivered to the user regardless of whether it is relevant or not. Filtrbox applies algorithms that filter content from an open search domain of publishers for contextual relevance. Filtrbox uses multiple factors to determine the contextual relevance of content and assigns a score called FiltrRank. The most important feature of the algorithm is that the contextual relevance algorithm learns from a Filtrbox user’s implicit interests and applies the implicit interest to future contextual relevance filtering. This means that the content delivered to the user is content that that specific user is interested in and not content other people are interested in. Contextual relevance filtering plays a large part in the reduction of information overload.
Unlike traditional RSS readers/aggregators, Filtrbox consumes content delivery formats beyond RSS. Filtrbox is capable of consuming both standard and proprietary content delivery formats.
One of our favorite past times at Filtrbox is figuring out fun but useful things to do with our technology. So in an effort to showcase our robust content filtering technology, we decided to put together FREE widgets that can be used to track news on each member of Team USA as well as the individual sports in which Team USA is competing.
For example, if you only want to follow Lopez Lomong, you can set up your widget to show news about Lopez only or if you care about Women Gymnastics only, you can set up your widget to show you news about Women Gymnastics only. In addition, you can set up different combinations of athletes and sports. Most olympic content consist of every bit of news about the Olympics and you have to do the filtering for the news that you are interested in. At Filtrbox, we do the filtering for you.
We have created two types of widgets, a blog widget to embed on your blog and a desktop widget that runs on your desktop. Both widgets can be found here.
My favorite widget is the desktop widget and because its my favorite, it has an additional special page for itself here.
Download the widgets and enjoy the Olympics.
Java + LAMP Developer
Join a dynamic, growing software company in Boulder, Colorado.
Basic requirements are:
* Solid experience with Java and LAMP
* System administration skills (a plus)
* Working knowledge of Information Retrieval and/or NLP (a plus)
* Must be energetic, motivated and creative
Please send your resume to TOM AT FILTRBOX DOT COM
NOTE: Prima Donna, high maintenance Rockstar developers, please do NOT bother sending your resumes!!!!
This is a pic of the new “Hop 2 Chautauqua” route map that I took this morning at the bus stop on Pearl and 23rd.
On Thursday (04/24/2008 ) last week, I had the privilege of talking to Dr. Jim Martin’s Natural Language Processing (NLP) graduate class, at the University of Colorado at Boulder, about the work that we are doing at Filtrbox and the role that current NLP students will play in the future of information technology. This blog post is the basis of my message to the class.
As I have written before, the problem that we face today is how to harness the data that is available on the web so that we can apply meaningful interpretation to it using applications. This problem is rooted in the assumption that the data that is stored on the web is “unstructured”. Unlike the majority of the data processed by applications today which is stored in some form of a structure e.g. a relational database, the data on the web is not so, as its is perceived as discrete pieces of data scattered all over the web.
I told the class that part of what I am doing at Filtrbox is an attempt to prove that the data on the web is not as “unstructured” as we may think today. Within that data, there is a lot of structure, relationship and general interconnectedness no matter how “discrete” we may think it is. With effective mining of the data and good applications, we can apply interpretation to the data and produce meaningful information. However, we are still far from applications that can apply effective interpretive meaning on this data. The reason for this is that we have to address the problem of information retrieval (IR) first before we can get to the writing of applications.
To recognize where we are today on the continuum of web data information retreival and applications; a look at the evolution of enterprise applications gives us a great analogy:
Enterprise applications are where they are today primarily because they have a structured data storage model (Relational Database or RDB) and a standard access model (Structured Query Language or SQL). Before there were enterprise applications that we know today, there were only RDBs and SQL. While RDB work dates back to the 1960s, the RDBs that the majority is familiar with today had their beginnings in the 1970s. The first (or widely believed to be) commercially available implementation of RDB+SQL was Oracle, then known as Relational Software, in 1979. This provided the ability to query an RDB for data using SQL but no applications as we know them today. Analogizing this with the web, this is where we are today. We can go on Google or our favorite RSS readers (RDB analogy) and query for web data using a weak REST API or search form (SQL analogy) but we have no applications comparative to what is in enterprise today to interpret that data. So simply put, today we are where enterprise applications were in 1979.
My message to the class was that applications like Filtrbox are starting to barely scratch the surface with respect to the implementing of applications on top of web data. That is because, although its 2008, we are still in 1979. The stumbling block is the perception of the “unstructured” nature of web data. Today’s NLP students will play a large role tomorrow in identifying and establishing structure in the “unstructured” web data in order to move us beyond 1979.
At Filtrbox we are looking for a Flex developer to join our team. If you meet the requirements below, send a resume to: TOM AT FILTRBOX DOT COM.
*Working knowledge of Flex
*Solid experience creating Web 2.0 UIs
*Actionscript 2 or 3 (must be recent)
*Flash 8 or 9 (must be recent)
*Must be energetic, motivated and creative