For a while now, I’ve been toying with the concept of an attention profiling service. Over the course of 2010 I’ve started building a (pretty sophisticated) prototype and it has now taken the shape of a startup that has great potential. For the time being, it’s called Reccoon.
Reccoon in Short
Initially, Reccoon will be an Open API that can be used by third-parties to analyze a person’s interests. Send Reccoon a Twitter username or a Facebook ID, and Reccoon will return a comprehensive semantic attention profile – all based on a person’s online activity. These profiles can be used by third-parties to provide greater relevance and personalization.
As you might suspect, there is a lot of data-analysis going on to make this happen and scale is a central theme. To make the Reccoon infrastructure highly scalable and the profiling service unique, Reccoon has a few tricks up it’s sleeve. This makes it very interesting for third-parties and could result in the option of a lucrative ‘buyout exit’. More about all of this in person.
At a later stage, Reccoon can turn its focus on the consumers. In doing so, we will make sure that there is more user interaction around the tools provided by Reccoon. Consumers can control their interests and attention, they decide which third-party can look into their attention data. And ultimately, Reccoon will monetize stored attention.
Not convinced this could make us filthy rich? Talk to me, and I will convince you. Right now I’m keeping media exposure to a minimum, but once we start our correspondence, I will send along screencasts, a business overview and competitive analyses.
About Me
My name is Dominiek, I consider myself to be a hacker that can fly high and dive down deep when necessary. I have a passion for building web applications, integrating with data services and build out a cool service. My strong suit is technology strategy and technical tactics. I’m sure you can find out more about me by googling around.
About You
I hope that you have these characteristics:
- You are highly analytical
- You are disciplined and more organized than me
- You are more perfectionistic than me, you want stretch the extra mile
- You are fucking smart, but modest about it ;]
And this frame of mind:
- Not scared of great ambition
- Willing to take on big challenges
- Flexible attitude (e.g. spend some time overseas, willing to go full-time at the right time)
- Risk tolerant (but not suicidal)
And I expect you to be able to dive down deep. That is, actually write code and work on the prototype. Reccoon is a high-tech focussed startup and a lot of stuff needs to be build, and in a way the founding team is part of the IP that makes a buyout interesting.
Last, but not least. I’m looking for either of these two skill-sets: (The post-founding team can be adjusted to it)
Data Wizard / Intelligent System Mastermind: Solid computer-science skills, ability to write complex algorithms and recommender systems, interest in AI and statistical algorithms.
OR
User Experience Joker / Product Development King: Good product/web abstraction, concrete frontend skills and an interest in building interfaces that solve information overload problems.
OR
You think I’m full of shit and you will tell me why YOU are the perfect Co-founder.
Get in touch
Finding the right partner is not easy, and I will allocate a significant time frame to find the right match. I assume we will collaborate on something small first, and then start putting in more time later.
If interested, please contact me at cofound@dominiek.com!



What people fail to understand about RSS
About two weeks ago there has been a heated debate over the future of RSS – the standard for subscribing to news feeds. Like many technological concepts, RSS can mean many things and needs to be looked at from multiple angles.
RSS, The Consumption of Long-form Content
MG Siegler wrote in a recent TechCrunch article: “It’s a mass consumption tool, not consumption tool for the masses”. I think this is a great point, because one of the main problems with consuming information through for example Google Reader is that you need to go through so many piles of crap to find something interesting.
Consuming long-form content is important, but it needs to happen when there is a very high level of attention. To find that piece of long-form content, you want to go through many pieces of short-form content, not unnecessarily read piles of long-form content. It’s questionable whether headlines are good enough to do this, I think not. I think you need a lot of ‘activity’ around a certain piece of long-form content for it to reach a good attention level.
This long-form content can be much more than just an article or a book, it’s anything that takes up time (movie, song, event, interaction, game, talking with someone, traveling somewhere, etc). This time that is spend needs to somehow be in sync with the attention of that ‘consumer’.
The consumption of information is not going to happen either through an RSS reader interaction or a noisy social network interaction. It’s going to be something new, and attention and relevance is going to be key.
There have been several alarmists screaming that the internet is making us stupid. I do agree that the internet is changing our brain – sensing what’s happening and having a more ‘symphonic intelligence’ (like a orchestra conductor) are an increasingly important skill-set. But it’s not going to happen through the mass-consumption of shallow tweets, it’s going to be through zooming. Sensing what’s going on and digging deep into places that are relevant.
RSS, The Subscription Interaction
The adding of new feeds from a site is another way of piling on noise to your ‘reading list’. Browsers now all support RSS auto-discovery of feeds, but who’s really using that? I’d love to see some statistics. Do you add Twitter RSS feeds or Delicious Bookmark feeds to your Google Reader? Perhaps you do.
Google Reader allows you to search for blogs which eases the pain of adding new subscriptions, but it’s still a subscription to a website. Much better would be a client that learns based on your implicit interests (behavior, interaction) and explicit interests (users, keywords, companies). Basically, getting rid of the ‘containers’ and mixing up the data streams. Let the data flow to the right attention (Synaptically!).
RSS, The Data Standard
I’m a huge fan of open standards, but I’m an even bigger fan of getting shit done. One serious practical obstacle with RSS is that it’s built on XML. I used to love XML until I started using JSON and I think many developers will agree with me. To summarize a long list of benefits, JSON reduces the time it takes for developers to integrate.
RSS is also not very extendable, which is horrible in an era where we have a serious need for meta-data. Atom is much better in that respect and a great example of it is Atom Activity Extensions.
RSS, The Feed Technology
Feeds are passive, non-real time and non-event driven. This poses severe practical limitations to RSS as a technology. Real-time carriers as Twitter have appealed greatly to developers. Why is that?
Twitter is not solving all of these, but is already solving many of them. It’s time that we create an open version of the Twitter Stream API, one with a lot of meta-data and with the ability to really extend the protocol.
Pubhubsubbub is a nice attempt, but it’s not meeting all the above needs and the stuff that’s out there is very hard to set up. Also, it’s very content-centric. The standard talks about ‘content, subscriber and publisher’. What about data? Big pipes of data flowing everywhere? Is the temperature sensor in my fridge a publisher? Is the smart algorithm that’s processing that ‘content’ a consumer? It’s just too oldskool.
XMPP is also something I was very excited about a while back, but what happened to it? I thought it would propel us into the ‘active web’. Twitter completely ditched XMPP and so have other non-nerds. I’ve tried doing stuff with XMPP too, it was a horrible technology to work with if you’re not building an IM client.
I think there is a huge opportunity here to accommodate the needs described here (technology and business wise). Execution will be key there, this means getting over our infatuation with some of the standards out there that are practically undesired. XMPP and Pubhubsubbub look good on paper and the nerds love it, but we need real post-1999 open standards.