Monkinetic Weblog

So far, Apple's doing all the right things with the new iPhone SDK. AWESOME.

how-useful-for-distributed-sites tags: ccc tp_commentcount: "3" tp_favoritecount: "0" tp_urlid: 6a010534988cd3970b0120a55cea62970b

#ccc; padding 1px;" />

Yesterday Google released a new contacts API, which has social network operators scrambling to implement.

Have you ever been on a web-site that asked you for your Google username and password so that it can import your Gmail contact list? Did you think twice before giving out that information, hoping the web-site would not use it to access your credit card information stored with Google Checkout? Now you don't have to!

We're happy to announce the availability of our Google Contacts Data API that gives programmatic access to your contact list. The contact list is shared among Google applications like Gmail, Reader, Calendar, and more.

This is exciting news for those of us working on DiSo -- it would be great to give users the option to add their Google Contacts to their friends. Well, at least until I started reading the Developer's Guide. The API (like many of Google's APIs) requires AuthSub support in the client, which requires registering your site with Google:

Note: You must register your application domain with Google before you can use AuthSub with the Contacts Data API.

It's my understanding that this means that any blog owner who wanted to use a hypothetical DiSo Google contacts import would have to have registered their site with Google, which sounds like a huge roadblock for us. Am I reading this wrong? I'd love to hear from other developers on this.

#000000;"/>

how-useful-for-distributed-sites

#ccc; padding 1px;"/>

Yesterday Google released a new contacts API, which has social network operators scrambling to implement.

>Have you ever been on a web-site that asked you for your Google username and password so that it can import your Gmail contact list? Did you think twice before giving out that information, hoping the web-site would not use it to access your credit card information stored with Google Checkout? Now you don't have to!

>We're happy to announce the availability of our Google Contacts Data API that gives programmatic access to your contact list. The contact list is shared among Google applications like Gmail, Reader, Calendar, and more.

This is exciting news for those of us working on DiSo -- it would be great to give users the option to add their Google Contacts to their friends. Well, at least until I started reading the Developer's Guide. The API (like many of Google's APIs) requires AuthSub support in the client, which requires registering your site with Google:

>Note: You must register your application domain with Google before you can use AuthSub with the Contacts Data API.

It's my understanding that this means that any blog owner who wanted to use a hypothetical DiSo Google contacts import would have to have registered their site with Google, which sounds like a huge roadblock for us. Am I reading this wrong? I'd love to hear from other developers on this.

getting-the-stuff-from-the-place-to-the-thing tags: "" tp_commentcount: "0" tp_favoritecount: "0" tp_urlid: 6a010534988cd3970b0120a5b36895970c

Recorded another quick podcast on the way to church this morning, on learning how to get stuff out of MT and onto a page...

Drivetime Debrief - Getting the stuff from the place to the thing.

Recorded another quick podcast on the way to church this morning, on learning how to get stuff out of MT and onto a page...

My grandfather, Marion Richard Ivy, veteran of 3 wars (World War II, Korea, and Vietnam), retired teacher, master woodworker, hobbyist gemcutter, man-about-the-house, and all-around awesome grandpa, turns 21 today! Someone get that man a beer! :-)

on-movable-type tags: "" tp_commentcount: "5" tp_favoritecount: "0" tp_urlid: 6a010534988cd3970b0120a5b36afb970c

On my drive home yesterday afternoon I called up BlogTalkRadio's Cinch service and recorded some thoughts on my early experiences with Movable Type, which I'm looking at while researching some stuff for DiSo. Topics covered:

• installing MT on OS X

• general UI

• blog menus v. system menus

• extending Movable Type

Drivetime Debrief - On Movable Type

learning-a-platform title: Drivetime Debrief - Learning A Platform slug: drivetime-debrief---learning-a-platform tags: podcasting, posdcast, wordpress, blogging, drupal, movable-type tp_commentcount: "1" tp_favoritecount: "0" tp_urlid: 6a010534988cd3970b0120a5b3669e970c

Quick recording today on the way home on how I get into a new platform, touching on Wordpress, Drupal, Movable Type and more.

Drivetime Debrief - Learning A Platform.

On my drive home yesterday afternoon I called up BlogTalkRadio's Cinch service and recorded some thoughts on my early experiences with Movable Type, which I'm looking at while researching some stuff for DiSo. Topics covered:

Quick recording today on the way home on how I get into a new platform, touching on Wordpress, Drupal, Movable Type and more.

Sorry for the dearth of content here lately, but life has been a bit overwhelming. One link for you: I've started an Election 2.0 group over on Ma.gnolia (waves at Larry), where I'm bookmarking "Links about new trends and ideas in election law, theory, and practice", as well as links relating to this year's election. It's a public group - feel free to join, contribute, and follow along. Please keep it on-track and respectful!

I'm using the Internet Archive/Wayback Machine to compile a Visual History of Redmonk.net.

The Existential DiSo Interview from Chris Messina on Vimeo.

Just wanted to follow up my post of the other day with a comment I just posted over on The B List.

I was browsing my own archives, and came across this post from Dec. 17th, 2004:

Tim Bray has a ongoing (ha) series of predictions for 2008, generated as a response to this request from Sun.

This started out as a post to the diso mailing list, but drifted. ;-)

I ran across a link to this morning, and while it's a technically interesting application, I can't help but see it, at best, as a complete dilution of what OpenID is supposed to mean, and at worst, an intentional abuse of OpenID and a perfect tool for spammers.