So I started looking for a Facebook application that would do just that. To my amazement I discovered that I could not find any application that would do the job in decent way (my definition of “decent” anyway).

Existing applications that I did not like enough included Social RSS, Networked Blogs, Involver, Facebook Notes and some others that I wouldn’t even consider.

I didn’t like Social RSS mainly for two reasons:

1. I don’t like ugly user interfaces (they don’t make me feel good about myself, my taste etc.)
2. It didn’t (at the time) use the Facebook Stream API and thus didn’t provide any distribution of posted stories to the news feeds of the Page’s fans etc.

I didn’t like Networked Blogs enough also mainly for two other reasons:

1. It was a pain for me to claim the RSS feeds from my social network due to a number of silly restrictions that were out of my control including restrictions imposed by Networked Blogs itself.
2. I felt it was built for a different purpose than the one I needed it for and frankly I didn’t even like the whole concept enough.

I rejected Involver apps because although it was an obviously serious professional effort, I found it to be ridiculously expensive for my non-for-profit activity in Blues.Gr and I was also unhappy with the fact that its functionality was broken down to many different smaller applications that were sold separately.

Facebook Notes was using the Stream API but it was not doing what I wanted to do. I wanted to post news from my site and directly link back to my site from my Fan Page. Notes was copying (importing) the news from my site to Facebook and then was distributing links to those copies instead. That’s not what I wanted. Moreover it didn’t look nice either. The format of the content was being messed during import and display and the whole thing just was out of the question.

So I thought why not write my own application for the job anyway? How hard could that be?

I started (on January 19th 2009), by writing a blog post on the internal blog I maintain for logging ideas with my business partner, and a few days later we decided to work on the project.

So RSS Graffiti was born. We initially called the project RSS Minifeeder (because at the time Facebook was calling the current “news feed” as “minifeed”). Later looking for a better name I came up with the word “graffiti” as representing the activity of writing on a wall (often in an aesthetically pleasing way). The .com domain was free; time was running out; hence the name “RSS Graffiti” was coined although it is not the most clear and straight forward name declaring what the application does.

Me and Dimitris started working on RSS Graffiti on January 21st, 2009, and devoted 16 man-hours per week to the project. RSS Graffiti version 1.0 Alpha was released 24 calendar weeks later (roughly 400 man-hours). RSS Graffiti version 1.2.1 Beta was the first version to be listed on Facebook’s Application Catalog (on August 22nd, 2009) and essentially it was the first version exposed to the open public (and thus we consider August 22nd 2009 to be the starting date of the application).

Four months later, RSS Graffiti is currently added to 17.000 walls, and actively publishes stories from 17.000 feeds to the walls of 2.500 Facebook Profiles, 5.500 Facebook Fan Pages and 500 Facebook Groups. These numbers are obviously a bit rounded up or down to be easier to read. They change by the minute anyway.

RSS Graffiti is still in Beta (current version is 1.8.0 Beta at the time of writing this) and is available as a free beta service while plans for premium services are also being considered for Q1 2010.

Why? Simply because there is always a next big thing after the last.

I came to realize that if I talk about my work a posteriori, then I have to make a case out of it and present it as such. That’s a big project on its own and needs time I don’t usually manage to find and devote. That’s often called marketing.

Still, work in progress is always worth a look at and at the same time is often more relevant to what other people are currently doing. So why waste all the energy I put in my projects, in just developing them, instead of adding a tiny extra bit of effort to let others know what work is in progress. That will add up to less than the time I need to publish a posteriori and at the same time, solve the problem of "no marketing".

The simple implementation of my "what do I do" series is just:

1. use my blog
2. add two or three categories to it

So I am adding these categories to my blog and start ASAP, then take it as it comes:

1. Current Projects
2. Projects On-Hold
3. Past Projects

Work under way is going to be published under "Current Projects". As soon as something is history, it will move to the "Past Projects" category. Finally, as some projects are occasionally put on hold while others take precedence, I thought of adding a third category for them to move in and out.

This post will remain for reference as the oldest post in all three categories.

So here we go…