As far as I know, a moblog is made by taking photos with your cell phone, sending them to some address, and then automating their inclusion on web page as a blog entry.

So I thought, here's a problem, how can I solve it? Looking at my Sprint PCS cell phone I found that when I email the photo to myself, the received email contains a thumnail of the image in the message and a pointer to the larger image on the Sprint website. I figured out how to parse the email to obtain the pointer URL, and then use the UUID-like information in the pointer to isolate the exact image location. To implement my own moblog-like API, the next step would be to retrieve the image binary and store it locally, followed the the automated generation of a new blog entry having the local photo as the blog body and the original email message subject as the blog title.

Now this seems like a very precarious solution. For one, if anything in the way Sprint makes the photos available changes, i.e. the pointer url style changes, then my adhoc moblog API would break. Further, this doesn't even begin to address what to do I wanted to add moblogging for my wife's Verizon phone.

Is there any standardization on how cell phone photos are handled by vendors like Sprint or Verizon? Do they have official API's on how to access the images?

Mystefied by moblogs, Steve