Tahiti gets a name and an initial code push

I haven't given a real update on Tahiti since my post last September announcing that I was putting it on hold. That's mostly been true since then. My schedule has prevented me from finding time to work on the project. In that time I've worked as a consultant with two different companies, completed multiple projects, presented at two conferences, attended two other conferences, and completed two full time semesters at Columbia.

However, I've still been thinking about the project and trying to devise a plan to get a prototype out. In January I decided to team up with Mint Digital to help out with design work while I did some Ruby consulting for them. I worked with their designers and put together some wire frames to solidify my ideas on the project and even came up with a proper name: Filterly.

My hope was to work on it during the spring semester, but commitments in and out of school kept me from finding time to code. Well now that it's summer and I'm not in school, I've been sneaking in some time here and there while not working at Mint. I written some of the back end code for crawling and updating feeds, which was the source of my recent posts about background processing and message queues.

I finally pushed out some code to EC2 and it should be running full time from here on. Right now it's just back end stuff and a landing page, but it's a start. If you're curious about what the hell the goal of the project is, please visit the landing page at Filterly.com where I lay out the basic idea.

I'm also posting this so that if people find the Filterly.com crawler in their server logs, this will have something more than just a note that I'm not working on it any more. Ok, enough of this pointless blather. I promise my next post will be more interesting. Probably about my EC2 setup and my plan to spend as little as possible on hosting costs.

Comments

[Benjamin Stein]

I *better* see a filterly.com crawler in my blog's server logs or I'm gonna be sad!