@JavaWoman: Regarding an API. We will have an API to post & manage your journal entries. The hang-up right now is simply because our current API infrastructure was not setup to really "impersonate" anyone - it's more of an official scraping mechanism.
Now that we have content that we hope/expect people to update regularly, we need to incorporate "authorization". Right now I'm leaning towards moving us towards OAuth for specifically this reason.
Lastly I am very eager to see maximum integration with other tools (IRC, IDE's, etc...). I am a little concerned with bridging from Twitter, however, for the same reasons u mentioned above: how to ensure our content stays technical/relevant?
Twitter is fairly context-free, and while many people tend to post Ohloh-relevant entries, I am wary of random stuff showing up here (e.g: "latte is scalding hot!", "sunny this afternoon", etc..
Thoughts?