[twitter-dev] update_profile_image api issues
I have an app that posts new profile images using update_profile_image in the API. as of about 3 some weeks ago (rough guess) the images uploaded are coming up broken, though I'm still getting a success status. I dug through this group and found a curl example for testing this API feature: curl -F 'ima...@path/to/image' -H 'Expect:' -u USERNAME:PASSWORD http://twitter.com/account/update_profile_image.xml I ran that in the terminal and got a xml return that seemed to indicate success, it showed me the same (or similar) out put as /users/ show/username.xml, with the exception that the new profile image I used in the curl command is not represented, instead it's still the previous image, but on twitter.com/home the image is broken. I haven't changed my code, but I don't know how to rule my code out. Is running this through Charles proxy the next step here, or is this a known issue? thanks +Clint
[twitter-dev] Re: Introduce yourself!
Hey all- My name is Clint, I'm a web and Cocoa developer from Missouri, and I've recently released my first beta app called Faces. Faces manages your profile pics across your various Twitter accounts. You can keep a collection of images for your profile pics and upload them to any of your Twitter accounts with a simple drag and drop. Here's a link to an announcement post which has a link to download the app for those interested: http://ctshryock.com/2010/04/introducting-facesapp-beta.html Faces is still a beta but largely complete. Any feedback is welcome at supp...@scary-robot.com Thanks +Clint -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Encrypt access key, secret, or both?
I'm getting up to speed on OAuth and I haven't found a clear answer in the existing threads; In my desktop app I request an access token and get a key and secret back from Twitter. For storage, is it necessary to encrypt both of those, or simply the secret? Thanks +Clint
