update_with_media not supported

[mwotton]

https://dev.twitter.com/docs/api/1/post/statuses/update_with_media

on the roadmap?

[mbbx6spp]

Now there is a need, sure thing! Let me review it tomorrow and give you an ETA.

[mwotton]

fantastic, thanks:)

[mbbx6spp]

So I looked into it and it requires a little bit of working around the oauth gem which doesn't currently support multipart POST. I am working on something to get around this locally and should be able to cut a release worthy version later this week.

Currently the client side API looks like:

client = Twitter.new(...all your oauth stuff in here...)
client.status(:post, :media => {:filename => "your_image_file.png", :content_type => "image/png", :body => "===YOUR DATA HERE==="}, :status => "Your awesome text status here.")

[mwotton]

Cheers. I've got a demo at Launch in the next couple of days, so I've had
to switch over to the nunemaker gem, but there's something very sketchy
about reconfiguring the module every time you want to send a tweet as a new
user - looking forward to switching back.:)

possibly unrelated, but is there an approved way of sending tweets
asynchronously? eventmachine integration etc?

mark

On Mon, Mar 5, 2012 at 3:10 PM, Susan Potter <
[email protected]

wrote:

So I looked into it and it requires a little bit of working around the
oauth gem which doesn't currently support multipart POST. I am working on
something to get around this locally and should be able to cut a release
worthy version later this week.

Currently the client side API looks like:

client = Twitter.new(...all your oauth stuff in here...)
client.status(:post, :media => {:filename => "your_image_file.png",
:content_type => "image/png", :body => "===YOUR DATA HERE==="}, :status =>
"Your awesome text status here.")

---

Reply to this email directly or view it on GitHub:
#18 (comment)

A UNIX signature isn't a return address, it's the ASCII equivalent of a
black velvet clown painting. It's a rectangle of carets surrounding a
quote from a literary giant of weeniedom like Heinlein or Dr. Who.
-- Chris Maeda

[mbbx6spp]

Sadly still in progress on pull request #20. Will sleep on it and return to it over the weekend. Receiving 403 HTTP status code consistently and appear to be within multipart form data specification. I am sure it is something small that I just haven't spotted yet. Will post my raw HTTP request to Twitter.com API discussions and see if anyone else sees it while I sleep:)

[mbbx6spp]

For my own reference, I posted my 403 dump here: https://dev.twitter.com/discussions/6226