Archive for February, 2006

Scrapi

Tuesday, February 28th, 2006

One of my favorite things out of MashupCamp is the word scrAPI.

The biggest challange in designing co.mments is figuring out how to identify comments. We could use comment feeds, but most blogs don’t support them. We can invent a new API and sit around waiting for bloggers to support it … some day. There are other solutions, but the one I found out to be the simplest is to just scrape the page and look for comments.

So essentially, you can think of each blog as having an API. A scraping API. Not all of them have it, and some are better than others, but for the majority of blogs, it’s good enough.

And not just for comments. Over the next few weeks, you’ll see a few additions that are currently in the works. I’m looking at ways to add authors, so you can track all comments made by a given person, and a way to add tags so you can drill down into conversations other people are tracking.

It’s all a matter of adding more features to the existing scrAPI.

And more on scrAPIs, from Thor Muller of RubyRedLabs:

The most exciting thing for me about Mashup Camp was seeing clearly the contours of an emergent phenomenon now in its earliest stages. We have APIs for only a miniscule portion of the data providers out there, and this is unlikely to change anytime soon. But we are starting to see a new breed of home-brewed APIs built on top of the screen scrapers we’ve all been writing and maintaining for years—scrapers that pull crime stats from police blotters, address data from Craigslist apartment listings, mp3s from web sites.

And of course there are ways to improve on the scrAPI, with a touch of Microformats. For bloggers, that’s the easiest and quickest solution to make sure comments are easily tracked. I’ll get to that in a future post.

Computers are wierd

Tuesday, February 28th, 2006

I woke up this morning to find two complaints that co.mments is not working, and a server log that looks something like this:

SystemStackError: stack level too deep in http://someblog/…
SystemStackError: stack level too deep in http://someblog/…
SystemStackError: stack level too deep in http://someblog/…
SystemStackError: stack level too deep in http://someblog/…
SystemStackError: stack level too deep in http://someblog/…

And it just went on and on.

That was a bug from last week, but it only affected very few blogs, not all of them. And besides, I fixed it during the migration along with a few other improvements. Somehow it found its way back. I don’t know how.

It’s gone now. I hope for good. I also rolled in a few other improvements that will smooth things up.

Home sweet home

Saturday, February 25th, 2006

Welcome to the new home of co.mments.

The last couple of weeks were a bumpy ride on an old server with a sluggish Internet connection. It was painful, it was slow and occasionally it would just stop the connection. I thought it would be good enough for the first month, but I didn’t expect that many users.

Now the move is over. We have a brand new server, faster and with a better Internet connection. It feels like stretching out after a long flight in coach class.

Oh, and you’ll probably notice a slight site redesign. More breathing room.