nicholasjon.com :: a weblog >> posts tagged: twitter

Twitter API Goes Geo

nicholasjon@nicholasjon.com (Nick) — Mon, 05 May 2008 15:59:22 GMT

I think including geography is going to be the killer feature in the next round of webapps. I’ve been waiting for Twitter to get in on the action. This will be cool.

Link: http://blog.programmableweb.com/2008/05/02/twitter-api-goes-geo/

nicholasjon 797650063

nicholasjon@nicholasjon.com (Nick) — Mon, 28 Apr 2008 03:31:01 GMT

Alright, too windy for kites. Just snapped the main spar in my Revolution. Damn.

Twitter in plain English

nicholasjon@nicholasjon.com (Nick) — Thu, 13 Mar 2008 02:07:20 GMT

By CommonCraft

nicholasjon 765778431

nicholasjon@nicholasjon.com (Nick) — Sun, 02 Mar 2008 21:46:55 GMT

Just finished cleaning up after a badly botched software deploy that has finally enabled Twitter support on my blog.Nick Olejniczak

Twoosh

nicholasjon@nicholasjon.com (Nick) — Thu, 24 Jan 2008 20:14:05 GMT

My first twoosh:

Thank you VH1 for reminding me that in 1984, during the making of Ghostbusters, Ray Parker Jr. was basically the poor man’s Michael Jackson.

Perfection, 140 characters at a time.

Twitter Fun

nicholasjon@nicholasjon.com (Nick) — Fri, 11 May 2007 05:27:11 GMT

In celebration of a little free time Sunday afternoon, I sat down and finally whipped together my first mashup.

I decided it would be fun to mess around with Twitter, because everyone is. And I decided it would be fun to play with the Yahoo! Maps API, because everyone else seems to be using Google’s. So I set about trying to visualize Twitter posts geographically.

Turns out, that’s pretty darn easy. (Probably why it’s already been done, but that’s okay.)

What I’ve got is a first cut, but I’m pretty happy with it. So now I’m curious? What else should it the map do? Let me know in the comments.

Scaling Rails via Twitter

nicholasjon@nicholasjon.com (Nick) — Sun, 15 Apr 2007 16:14:42 GMT

The Twitter folk aren’t pleased with Rails scalability.

DHH points out the way their app was configured it was never really going to scale anyway, and that they certainly could improve their performance with more caching and more database servers. He does end on a sort of Rails is open source, you can always fix it yourself note, which is a little disingenuine.

Brian McCallister responds to the whole thing with I think the best perspective of all.

Update: Problem solved. (Dr Nic to the rescue.)

Update: And again. (This looks really promising.)

Update: And again. (Dr Nic again — he’s good.)