#Qaiku-api

when requesting status items they could include the mime type and URL of the media item as new properties of the JSON object, but how about updating?

@bergie Are classic multipart-posts an option? I believe, that having them and, alternatively, being able to specify URL of image should be enough.

I am against encoding binary-objects in json. That's an overkill

@indeyets sounds reasonable, and easy to implement. How does the internal API work for this @tepheikk ?

@bergie It would be nice to have also smtp-api for pictures. Sometimes it's easier to send picture as attachment than providing it publicly in internet. In that case I would like to get reply message with object id -- And possibility to send new picture as an reply for that Qaiku-post (--> several images in same thread).

@Ile you can already post picture Qaikus by email. Just send them as attachments to the APIkey email address. Picture-based replies are not supported yet, but there has been some discussion of providing that in the future.

@bergie Yes I know, but that's currently kind of human interface, my suggestion is more features for using it from application

For example:

• posting new qaiku --> Qaiku sends confirmation message back. Message-ID is qaiku message ID, In-Reply-To has message id of your original mail (to link to my system)
• Sending replies: By defining In-Reply-To: Qaiku-Message-ID you can send replies (with or without images) --> Qaiku sends confirmation message back

@bergie I thought about this. I don't know how I could provide URL for image in my iPhone client.

Could you have endpoint for http upload (could be temp area) and then I could provide link to your temp with my as-unique-name I can generate on client side?