[twitter-dev] When is permission level enforcement going to happen?
I know the date for this is today (June 30), but is it something that will be rolling out slowly throughout the day starting sometime soon, or is it going live at the *end* of today or how is that working? I don't recall seeing the details mentioned previously. I'd like to get an idea of when I should start the pot of coffee that will be necessary to deal with the inevitable tech support flood... l8r Sean -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Feedback wanted on Twitter + iOS
Ryan, On Jun 28, 2011, at 6:44 PM, Ryan Sarver wrote: We'd love to see your apps, give feedback and help make developing on Twitter and iOS 5 a great experience so let us know how we can help. Simple, open up access to DMs via the API. This. l8r Sean -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] 403 and 502 errors?
Since releasing Twitterrific 4.2, which uses the new OAuth flow, we're seeing customers reporting spurious 403 and 502 errors specifically when attempting to retweet or send DMs. Is there a chance something is amiss? l8r Sean -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Photo API?
Is there any third party API for interfacing with this new photo/video service? l8r Sean -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Ampersand
This is OT for this list, but you need to use NSString's -stringByAddingPercentEscapesUsingEncoding: method (or similar) to encode characters correctly for URLs. l8r Sean On May 27, 2011, at 9:10 PM, R wrote: I'm using cocoa and NSUTF8StringEncoding. When I post a sentence that contains the ampersand (), all text that follows is removed from the resulting tweet. How should I deal with the within a sentence (not URL) of a post? Thanks -- Ron -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] force_login on authorize?
I know there was some talk about adding this, and I may have missed it, but does /oauth/authorize support force_login yet? I know I could try it pretty trivially, but thought I'd ask here since I'm sure others with apps that support multiple accounts are also interested in the answer. l8r Sean -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Please confirm this OAuth flow ...
On May 19, 2011, at 9:53 AM, Tom van der Woerdt wrote: Also, don't display it in a WebView, use the normal browser instead and use a callback URL with a custom scheme - for example myapp://. Let the browser redirect this URL back to the app. Again, do NOT use a UIWebView - I'm pretty sure that that's against the TOS, and if it's not, it soon will be. Twitter - I need an official answer on this immediately. Is (or will) it be against the TOS to use an embedded web view for the OAuth flow now that xAuth is effectively useless? l8r Sean -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: GET :user/lists/:id/statuses stopped working
Yeah, changed the URL to this and it works now:
http://api.twitter.com/1/padems/lists/pademocrats/statuses.json
What's odd is it _was_ working before - something had to have changed
on Twitter's side.
Thanks.
On Mar 29, 5:09 pm, Cameron Kaiser spec...@floodgap.com wrote:
This just stopped working for me:
http://twitter.com/@padems/lists/pademocrats/statuses.json
It now returns this:
{request:\/@padems\/lists\/pademocrats\/statuses.json,error:You must
specify either a list ID or a slug and owner}
Anyone know what's going on?
Get rid of the @.
--
personal:http://www.cameronkaiser.com/--
Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com
-- Silly is a state of mind, stupid is a way of life. -- Dave Butler
--
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
[twitter-dev] GET :user/lists/:id/statuses stopped working
This just stopped working for me:
http://twitter.com/@padems/lists/pademocrats/statuses.json
It now returns this:
{request:\/@padems\/lists\/pademocrats\/statuses.json,error:You must
specify either a list ID or a slug and owner}
Anyone know what's going on?
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
[twitter-dev] Some general questions on displaying tweets
I can't figure out if I need the API to accomplish this or just using a generic user search and jQuery. My platform is PHP can someone give me a brief roadmap how to accomplish the following tasks page 1 (a widget) pull latest 5 tweets given a list of users --- this will never work because 50 tweets will happen before the last 5 ever get back but thats what the client wants --- this will display full name of the user --- this will display the date/time --- this will contain a link to view all from last 24 hours page 2 (after clicking view all) - the last 24 hours of our users page sorted newest first Paginated @ 50 tweets per page UserOne says - tweet one UserTwo says - tweet one UserOne says - tweet two UserSeven says - tweet one Do I need the API to accomplish this? Any thoughts ideas greatly appreciated. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Seeing duplicate Twitter User ID's under the same Username in our DB
Hello Twitter Support, We are seeing something really weird. We just noticed about 5,000 users in our database that have multiple User ID's under the same Username. Have you every seen this and know why it happens and how we can prevent it from occurring again? Thanks so much! Sean -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Seeing duplicate Twitter User ID's under the same Username in our DB
That is the problem. User ID's are not suppose to change, though in our DB we see the same screen name with a different User ID. Of the 5,000 users in the DB, some have 6 ID's, a few have 5, 4 and 3 ID's but many have 2 User ID's. We are talking 5,000 users being affected of 5 million users in our DB. Sean On Sep 13, 5:46 pm, Mark McBride mmcbr...@twitter.com wrote: One thought is that people change screen names at some frequency. IDs never change. ---Mark http://twitter.com/mccv On Mon, Sep 13, 2010 at 4:41 PM, Sean Callahan seancalla...@gmail.com wrote: Hello Twitter Support, We are seeing something really weird. We just noticed about 5,000 users in our database that have multiple User ID's under the same Username. Have you every seen this and know why it happens and how we can prevent it from occurring again? Thanks so much! Sean -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group:http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: garbage in json api response?
Twitterrific users have been seeing this for at least 2 hours, now. On Sep 3, 2010, at 8:47 AM, TheGuru wrote: +1, unable to parse timeline due to garbage in the XML feed. Many of our users are reporting the same problem. On Sep 3, 7:35 am, koujitaro kohura12345...@gmail.com wrote: Same phenomenon occured in xml. URL is belowhttp://api.twitter.com/1/statuses/user_timeline.xml?user_id=93771355 -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] How to get all Verified Users @ http://twitter.com/verified
Is there an API call or a quick way to get a list of all users on Twitter that are verified? I am updating this list, http://tweetphoto.com/celebrities, and was looking for a quick way to update it. Thanks for your help! Sean
[twitter-dev] Re: Early look at Annotations
XML option #2 feels like the best option to me, because it seems the most flexible, most forward compatible, and plays well with AWS: http://docs.amazonwebservices.com/AmazonSimpleDB/latest/DeveloperGuide/SDB_API_GetAttributes.html (that's my $0.02) _s. XML option #2 which is more verbose but allows for namespaces and keys to contain arbitrary data annotations annotation namespaceiso/namespace keyisbn/key value030759243X/value /annotation annotation namespaceamazon/namespace keyurl/key valuehttp://www.amazon.com/Although-Course-You-Becoming-Yourself/dp/030759... /value /annotation /annotations If we went with XML option #2 it may or may not be a problem that it isn't symmetrical with the JSON representation. On the other hand, JSON and XML tend to be culturally at opposite sides of the Pithiness Spectrum. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Introduce yourself!
I'm Sean Callahan, @CallahanSean, creator of http://tweetphoto.com, and have been working with the Twitter API since the fall of 2008. I now work with a team of seven who are very skilled at working with the Twitter API. Using the Twitter API we have created an extensive and easy-to-use photo sharing API and client libraries for Obj-C, Java and .Net. Other 3rd party developers in the Twitter community have developed client libraries for PHP and Python as well. Like you Abraham, we are constantly looking to improve our API. Please take a look at our API and let us know what we can provide the Twitter community to create an even better photo sharing experience. Please let me know how I can help you create a more social photo sharing experience in your application. The TweetPhoto API can be found http://groups.google.com/group/tweetphoto ~Sean On Feb 19, 1:20 pm, Abraham Williams 4bra...@gmail.com wrote: We have not had an introductions thread in a long time (or ever that I could find) so I'm starting one. Don't forget to add an answer to the tools thread [1](Gmail link [2]) as well. I'm Abraham Williams, I've been working with the Twitter API and this group since early 2008. I do mostly freelance Drupal and Twitter API integration and personal projects. I love seeing the creative projects developers build or integrate with the API and look forward to meeting many of you at Chirp. TwitterOAuth [3] the first PHP library to support OAuth is built and maintained by me, and will hopefully see a new release soon. I also built a fun Chrome extension [4] that integrates common friends and followers into Twitter profiles. The feature I would most like added to the API is a conversation method to get replies to a specific status. So. Who are you, what do you do, what have you built, and what feature do you most want to see added? @Abraham [1]http://groups.google.com/group/twitter-development-talk/browse_thread... [2]https://mail.google.com/mail/#inbox/12680cd0fa59011e [3]https://chrome.google.com/extensions/detail/npdjhmblakdjfnnajeomfbogo... [4]http://code.google.com/p/twitter-api/issues/detail?id=142 -- Abraham Williams | Community Advocate |http://abrah.am Project | Out Loud |http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: A proposal for delegation in OAuth identity verification
That is similar to what we are doing at TweetPhoto and it is working out fine. Feel free to check out what we are doing: http://groups.google.com/group/tweetphoto/web/oauth-signin Third-party apps share with us their app's consumer key and secret. We receive the same level of access to the third-party app using our photo sharing service. When two companies work together and are partners there needs to be a level of trust. Furthermore, developers can change their consumer secret at any time so their is no real issue with this method. There are a few integrations coming out soon with this method in place. Please let us know your thoughts and if you have any questions. Sean On Feb 11, 10:05 am, Brian Smith br...@briansmith.org wrote: Raffi Krikorian wrote: The term most frequently used for “delegator” is “relying party.” What you call the service provider is most frequently called the “identity provider.” What you call the consumer is usually called the “subject.” See OpenID, InfoCard, and other similar specifications for example usage of these terms. First, what I wrote about subject was misleading: the user--not the consumer--is the subject. i hear all this - it just gets a bit complicated with because we are conflating this with our oauth situation. This doesn't really have much to do with OAuth, because you are not trying to allow delegation of credentials--that is, you are not trying to allow the consumer app to let the relying party use the consumer app's OAuth access token to read/write the user's account. perhaps its time to move to an oauth + openID hybrid system. I don't know if OpenID really solves this problem well, especially for apps that aren't webapps. The subject doesn’t want the relying party to have access to the entire response from the account/verify_credentials request as if he had given the relying party read access to his account. I am not sure if account/verify_credentials returns sensitive information (information only available to apps that have been authorized by the user) yet, but I think it is likely in the future that it will do so. It would be prudent to have delegation use a different resource designed specifically for delegation. i think this is again a general case vs a twitter case. i think in the general case, the delegator would call some endpoint that would simply verify the identity through a HTTP code (2xx for success, 4xx for failure). twitter, as a special case, sends along the user object [as] part of it? account/verify_credentials discloses information that is private. For example, the HTTP header of account_verify_credentials discloses information about how frequently the user accesses twitter (the rate limit headers). If the user hasn't previously authorized (via OAuth) the delegator (relying party) to have read access to his account, then the delegator (relying party) shouldn't be able to get this information. Also, I think you should plan ahead for the case where account/verify_credentials returns even more sensitive information. If you were going to reuse an existing resource, I'd reuse users/show.format?user_id=username instead. But, AFAICT, it's much better to create a new resource for this purpose, and pretty easy to do so. I think the following would be a better protocol: Consumer to Relying Party: Give me RP-SIGNED-TOKEN, a nonce signed with your OAuth credentials for the relying party'sidentity verification service. Relying Party to Consumer: Here is the token RP-SIGNED-TOKEN. (This is done using whatever protocol the consumer and the relying party agree to use.) Consumer to Identity Provider: Here's RP-SIGNED-TOKEN. Give me IP-SIGNED-TOKEN, which is (RP-SIGNED-TOKEN, screen_name) signed with a signature that the relying party can verify is from the identity provider. Identity Provider to Consumer: I verified that the token was signed by the relying party identified by RP_ID. Here is IP-RP-SIGNED-TOKEN. (This is an OAuth-protected transaction using the consumer's credentials). Consumer to Relying Party: Here is IP-RP-SIGNED-TOKEN.Relying Party to Consumer: OK, let's continue on with whatever we need to do. (This is done using whatever protocol the consumer and the relying party want to use.) Notice in particular: (a) each server only has to process one request, (b) the relying part and the identity provider never have to communicate directly with each other, (c) the consumer (user) can control the level of security used in all the communication (e.g. TLS for everything), (d) IP-RP-SIGNED-TOKEN can be used as the assertion in the OAuth 2.0/WRAP assertion profile, if the relying party is using OAuth WRAP to authenticate the user, (e) the user and the identity provider can both restrict which consumers can sign into which relying parties for which users using this mechanism. Regards, Brian
[twitter-dev] TweetPhoto now setup for OAuth support
TweetPhoto now supports OAuth for photo sharing within third-party applications. http://groups.google.com/group/tweetphoto/web/authentication Let me know if you have any questions whatsoever. Sean
[twitter-dev] Re: How Does TwittPic Works ?
TweetPhoto offers an OAuth solution for uploading photos. Please check out the link below and let me know if you have any questions. http://groups.google.com/group/tweetphoto/web/oauth-signin Thanks! Sean On Feb 2, 7:04 am, Feras Allaou feras.all...@gmail.com wrote: Dear Sirs, I was trying to do oAuth to use Twitter API but I was surprised that TwitPic doesn't use this Authentication method ! so How could TwitPic publish it's name when it updates the status ? I mean if I use simple Auth method the message will be sent using API which means Twitter API. but When I was OAuth the sending method will be my Twitter Client , right ? So how does TwitPic sending method is TwitPic they don't use Oauth ? Regards, Feras Allaou
[twitter-dev] Re: OAuth Photo Support Now Available at TweetPhoto
All the other functionality in the TweetPhoto API is also supported using OAuth as well. Let me know if you have any questions. Sean On Jan 31, 9:01 pm, Sean Callahan seancalla...@gmail.com wrote: TweetPhoto now supports photo uploads using OAuth for all 3rd party application developers. http://groups.google.com/group/tweetphoto/web/oauth-signin Basic Auth may be depreciated soon so we created a way for you to allow your users to continue to uploadphotos. Please let me know if you have any questions or if I can help in any way. Sean
[twitter-dev] Basic Auth seems to be down right now - Last 10 minutes
Looks like basic auth is down. Anyone else seeing lots of login failures? Sean
[twitter-dev] iPhone Developers: Objective-C Library for TweetPhoto
We just released the Objective-C library for the entire TweetPhoto API. It is a set of drop in classes designed to allow you to get up and running quickly with the TweetPhoto Photo Sharing API. http://code.google.com/p/tweetphoto-api-objective-c/ This library includes every feature you'll need to manage the entire photo sharing experience within your application - from uploading photos, commenting, favoritng, and voting to social feeds, user feeds, and everything in between. Please let me know if you have any questions whatsoever. Sean
[twitter-dev] Help! Invalid / expired token. (PHP using Abraham Williams' library.)
I can't figure this out for the life of me. I've authorized my
application and retrieved the access token. The access token and
secret are stored in a database. Then I try to make a 'verify
credentials' query using Abraham's library, as shown in the example
code:
$connection = new TwitterOAuth($consumer_key, $consumer_secret,
$access_token, $access_secret);
$content = $connection-get('account/verify_credentials');
I keep getting the following error response:
{request:/1/account/verify_credentials.json?oauth_consumer_key=
[my_consumer_key]
oauth_nonce=1e10a10ba19315ee8c935f819e082b4coauth_signature=a99dyAMXN7vI
%2FZqRqzHPkKrgfWw%3Doauth_signature_method=HMAC-
SHA1oauth_timestamp=1259628414oauth_token=[my_access_token]
oauth_version=1.0a,error:Invalid / expired Token}
Does anyone know what could be causing this? I've checked and
rechecked the tokens and keys ad nauseum, so I think the problem is
somewhere else.
Thanks in advance!
[twitter-dev] Re: OAuth success but getting intermittent 500 Internal Server Error requesting access token
Getting the same thing, 500's from access token requests. This is affecting all of our new users. Any insight would be lovely! Sean Ping.fm On Nov 11, 12:29 pm, Yu-Shan Fung ambivale...@gmail.com wrote: Hi All, I've been getting a high number of 500 errors (about 50% of the time yesterday) after user authenticated via oauth, and I try to get the access token from twitter. The weird thing is that the error is not consistent, and the exact same code/setup works about half the time, with the same test user acocunt. I'm using the ruby oauth gem and here's the error it returns 500 Internal Server Error /usr/lib/ruby/1.8/net/http.rb:2097:in `error!' [RAILS_ROOT]/vendor/gems/oauth-0.3.5/lib/oauth/consumer.rb:199:in `token_request' [RAILS_ROOT]/vendor/gems/oauth-0.3.5/lib/oauth/tokens/request_token.rb:18:in `get_access_token' Any idea what could be causing this? Thanks, much appreciated! Yu-Shan -- “When nothing seems to help, I go look at a stonecutter hammering away at his rock perhaps a hundred times without as much as a crack showing in it. Yet at the hundred and first blow it will split in two, and I know it was not that blow that did it, but all that had gone before.” — Jacob Riis
[twitter-dev] Re: Lists API
Apologies, i must have missed it as well. On Mon, Nov 2, 2009 at 10:10 AM, Michael Steuer mste...@gmail.com wrote: Ah, great... I must have missed that announcement! Thanks, Michael. On 11/2/09 10:05 AM, Marcel Molina mar...@twitter.com wrote: It's available to all developers and has been since last Thursday. There are still some tweaks to be made but everything that works now should continue to be supported along side the changes and additions that will be introduced. On Mon, Nov 2, 2009 at 9:48 AM, Michael Steuer mste...@gmail.com wrote: With all the discussions on this mailing list about the Lists API, can someone please confirm, is the API now available to all developers or all of you in some sort of preferred position? Thanks, Michael. -- Sean Scott cell: 612.867.8133 portfolio: http://www.flickr.com/photos/92876...@n00/sets/72157613990263453/ profile: http://www.linkedin.com/profile?viewProfile=key=2242610 blog: http://www.twofortyeight.com/ other: http://twitter.com/kalisurfer
[twitter-dev] Re: Lists API
List API is in Beta. If you're in the beta you can play with it. If you're not in the Beta you can't play with it just yet On Mon, Nov 2, 2009 at 9:48 AM, Michael Steuer mste...@gmail.com wrote: With all the discussions on this mailing list about the Lists API, can someone please confirm, is the API now available to all developers or all of you in some sort of preferred position? Thanks, Michael. -- Sean Scott cell: 612.867.8133 portfolio: http://www.flickr.com/photos/92876...@n00/sets/72157613990263453/ profile: http://www.linkedin.com/profile?viewProfile=key=2242610 blog: http://www.twofortyeight.com/ other: http://twitter.com/kalisurfer
[twitter-dev] Re: Duplicate Tweets
Can I suggest: A RepeatTweet API. Permit the delivery of marked duplicate tweets on the Twitter side, with an API to allow external apps/services to integrate it. The system could permit (and only permit) RepeatTweets with a DuplicateOf tag indicating the duplicated tweet, sent through the API. This would allow Search to filter out duplicates, and other apps could filter out duplicates that the user has already seen/marked as read. This would also allow external apps/services to provide the scheduling. RepeatTweets could be rate-limited (say 5 per 24h per account) to reduce spam. This would facilitate most of the usage cases I've read in this thread -- except emergency services, where duplicated tweets shouldn't be filtered out because the duplicate text refers to a new/changed condition. Perhaps a whitelist of such emergency services should be exempted from the exiting duplicate filters. Regards, Sean Lindsay On Oct 16, 5:01 pm, John Kalucki jkalu...@gmail.com wrote: I don't know about paygrade, but more than a few Twitter employees follow i80chains during the season. We hear you. I just don't know what to suggest be done about the situation.
[twitter-dev] Re: API for marking tweets seen
I agree. I use multiple clients throughout the day and the ability to know where I left off is a huge plus so that I don't have to memorize what the last tweet I read was (especially if its been a while). Although it would be a bit difficult and can turn into a nightmare for the website. For example, with email, we must list all our email and if we have a lot of people emailing us (this is equivalent to people we follow), we end up with a backlog that we must go through and mark everything read by hand (or select all then mark as read). It can make things a little overwhelming, unless they are automatically marked as read once you log out (fetch only those since the last login). On Oct 7, 4:32 am, Theyagarajan S they...@gmail.com wrote: Hello, As someone who uses tweetdeck,web and my mobile client i would think if there was a way an app would know if the tweet was already seen by a user.One way i could think of is knowing/storing the least tweet (by timestamp) that was fetched by user with API/web, and any app that user will first fetch the last seen tweet time and request only tweet stream after the time. Has anyone else felt the need for this? Thanks Taggy
[twitter-dev] URGENT: Error Signing In Twitter Users on TweetPhoto API (Metering/Rate Limiting)
Hi Doug, Alex Ryan, We need your immediate help. Right now Twitter users are not being able to authenticate through the TweetPhoto photo sharing API at tweetphotoapi.com. 9 times out of 10, no one can upload a photo through the platform and receive, error message - invalid twitter username/password. The error we're receiving from Twitter: errorRate limit exceeded. Clients may not make more than 15 requests per 60 minutes./error It seems like the problem goes away at the top of every hour which could mean it is a metering and/or a rate limiting issue. Everything works for the first 7 to 10 minutes at the beginning of every hour and then no one can sign in to upload photos through our API. I think we've narrowed this down to being a sign in issue and need your immediate help. I've received reports about this over the last 72 hours, but could not replicate the issue from our end until now. I've whitelisted over 12 to 15 IP addresses in the past to prevent such issues and was always told whitelisting does not affect sign in issues. I am stumped. Everything has always worked fine with the levels of volume we have today. Please let us know if you can help. I am standing by on the phone if you need to call me. Thank you! Best Regards, Sean Callahan TweetPhoto.com Co-Founder Office (760) 230-5579 Mobile (760) 840-7468 Skype: seancallahan
[twitter-dev] Re: Change in API
So, I'm still having trouble. I have the following code (cribbed from
a tutorial) which is very simple and should work but does not:
Start of Code
?php
$twitter_api_url = http://twitter.com/statuses/update.xml;;
$twitter_data = status=Updating the API CAlls;
$twitter_user = [username];
$twitter_password = [password];
$ch = curl_init($twitter_api_url);
curl_setopt($ch, CURLOPT_POST, 1);
curl_setopt($ch, CURLOPT_POSTFIELDS, $twitter_data);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, 1);
curl_setopt($ch, CURLOPT_HEADER, 0);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_USERPWD, {$twitter_user}:
{$twitter_password});
$twitter_data = curl_exec($ch);
$httpcode = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);
if ($httpcode == 200) {
echo Congratulations, Tweet was posted correctly.;
}else{
echo Something went wrong, and the tweet wasn't posted.;
}
?
=End of Code =
Can anyone tell me what I'm doing wrong? (I have changed the username
and password values for this post, normally, they are correct.
Thanks
On Sep 4, 5:44 pm, Peter Denton petermden...@gmail.com wrote:
It may be that posts were changed to gets.
On Sep 4, 2009, at 2:21 PM, Sean Fawcett s...@fawcettassociates.com
wrote:
Hi:
A couple of months ago, I received an email from Twitter about some
changes in the API. I was, at that time, up to my eyeballs with a
time sensitive project and did not have time to follow up.
Now, I notice that a very simple function that I created, allowing a
user to fill in a text field from a web page and post a Tweet, no
longer works.
Is there something I missed? What do I need to do to make sure my old
code (March '09) now works with the API changes.
Any insight would be very helpful.
Thanks
Sean
[twitter-dev] Change in API
Hi: A couple of months ago, I received an email from Twitter about some changes in the API. I was, at that time, up to my eyeballs with a time sensitive project and did not have time to follow up. Now, I notice that a very simple function that I created, allowing a user to fill in a text field from a web page and post a Tweet, no longer works. Is there something I missed? What do I need to do to make sure my old code (March '09) now works with the API changes. Any insight would be very helpful. Thanks Sean
[twitter-dev] Does anyone have an ASPinfo.asp file they can share?
I am in need of an aspinfo.asp file to grab detailed system information on a windows server. I can't find one of those files to save my life. Can someone please email me one to s...@tweetphoto.com ??
[twitter-dev] Re: Announcing Twitterfall Reply Search service and API.
Very cool! I will definitely watch this project as it develops! On Aug 25, 7:50 am, x5315 red.ca...@gmail.com wrote: Have you ever seen your favourite celebrity ask a question, and you were wondering about the answer too? Or have you ever been taking part in a competition and been wondering who else was entering? The Reply Search service allows you to view replies to tweets based on their ID, or based on a username. For more details seehttp://blog.twitterfall.com/see-whos-replying-right-now orhttp://replies.twitterfall.com
[twitter-dev] Re: Developer Preview: Geolocation API
Quick question Ryan, because none of this will surface on Twitter.com will you keep the Location field for a users profile or is that going away when this becomes love? If it stays, will there be any specific changes regarding the location on a user's profile when this API becomes available? Sean On Aug 20, 5:28 pm, Lepton m...@myallo.com wrote: Perfect timing! My iPhone app about to be released has a lot to do with geolocation, and already uses Twitter to set and see locations of people. Myallo HotList tracks the hotness of people and places in your social universe partly through their locations. For example as a person gets nearer to you, they get hotter, if friends gather near a place, they and the place get hotter. I want to use these upcoming features to discover nearby people. You can preview the app via its documentation athttp://myallo.com/hotlist
[twitter-dev] Re: Issues with the API this morning?
The issue we're seeing at TweetPhoto is that no one can login to their account when using basic auth. Was informed by Twitter support that they are aware of the issue and are looking for a fix. On Aug 17, 8:53 am, Dewald Pretorius dpr...@gmail.com wrote: Lots of issues here (tweetlater) too. High-volume calls are again blocked by the edge defenses with connection refused. Exactly the same as last weekend. Dewald On Aug 17, 12:19 pm, CodeWarden paul0...@gmail.com wrote: Are there still issues with the API this morning? We have many of our UberTwitter users reporting timeouts when trying to retrieve timelines and send tweets. We are not using OAUTH. Any info would be greatly appreciated! -CodeWarden
[twitter-dev] Re: Issues with the API this morning?
I was starting to worry that something was wrong with Twobile (basic auth). Any news from the mothership on what's happening? On Aug 17, 10:42 am, Aaron Forgue for...@gmail.com wrote: My app, too, appears to be blocked. I can't even get status codes - the requests just timeout with no response. On Aug 17, 12:24 pm, Dewald Pretorius dpr...@gmail.com wrote: So, the general message is: Mayhem rules. I have no issues with Basic Auth (on low volume API calls). Login no problem. Dewald On Aug 17, 1:04 pm, Sean Callahan seancalla...@gmail.com wrote: The issue we're seeing at TweetPhoto is that no one can login to their account when using basic auth. Was informed by Twitter support that they are aware of the issue and are looking for a fix.
[twitter-dev] Re: Platform downtime is expected
Hi Ryan, I just replied to your email and also will post here in case you read this first. Maybe others will have an idea too as why basic auth is not working. Long story short - we were down for 3 days, up for the last 3 hours, and now down once again - no one can login using basic auth on our site http://tweetphoto.com. It so happens when I responded to your email about 3 hours ago everything was working fine - meaning I was able to login to TweetPhoto as were other users. Since replying to your second email basic authentication on http://tweetphoto.com is not working an no one can login to their account on our domain. I'm not sure why basic auth is not working when you said only OAuth should have been affected. With that said, I have an idea as I've spoken to a few Rackspace customers. Is it possible that a range of IPs at Rackspace are being blocked/throttled preventing users from logging in through basic auth? I'm not sure why basic authentication came back online this morning and now it does not work. You asked me to respond to an email Alex sent, but I have not seen that. Please let me know what information you need to better troubleshoot this issue so we can resume service. As I mentioned in my email to you, I am willing to pay a monthly service fee as I'm sure other Twitter Developers are, to keep service running to TweetPhoto.com up 100% of the time. Please advise. Best Regards, Sean Callahan On Aug 16, 11:40 am, bosher bhellm...@gmail.com wrote: Thanks for the update Chad.. On Aug 16, 10:52 am, Chad Etzel jazzyc...@gmail.com wrote: Hi all, The API team is actively debugging the OAuth issues as we speak. Please be patient as we nail down the problems. Thanks, -Chad On Sun, Aug 16, 2009 at 1:43 PM, Andrew Baderaand...@badera.us wrote: On Sun, Aug 16, 2009 at 1:40 PM, bosherbhellm...@gmail.com wrote: How is it that all the oAuth apps out there are down, but others like TweetMeMe are not? TweetMeMe works just fine, how is that possible? HTTP Basic Auth still works I believe, as do any pre-problem OAuth tokens issued. ∞ Andy Badera ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me:http://www.google.com/search?q=(andrew+badera)+OR+(andy+badera)- Hide quoted text - - Show quoted text -
[twitter-dev] Re: Platform downtime is expected
Hi Ryan, When I sent the email 30 minutes ago I was not able to login. Now, like you, I was able to login. Now it is a sporadic issue. I will get you the info you need to those 5 questions. Because our current environment at the Rackspace Cloud is shared I need to call them. Basically, it is simply a basic auth issue. We're not calling anything, but that. User's cannot login. The IPs of the Rackspace Cloud that I am on are (Primary) 74.205.61.228 and (Secondary) 74.205.61.229 Not sure if this helps. Please advise. Sean On Aug 17, 3:37 pm, Ryan Sarver rsar...@twitter.com wrote: Sean, I was just able to log into TweetPhoto using my basic auth credentials with no problem. Please test again and provide any of the additional details that you can: *Copying from Alex email to make sure its consistent 1. The IP of the machine making requests to the Twitter API. If you're behind NAT, please be sure to send us your *external* IP. 2. The IP address of the machine you're contacting in the Twitter cluster. You can find this on UNIX machines via the host or nslookup commands, and on Windows machines via the nslookup command. 3. The Twitter API URL (method) you're requesting and any other details about the request (GET vs. POST, parameters, headers, etc.). 4. Your host operating system, browser (including version), relevant cookies, and any other pertinent information about your environment. 5. What kind of network connection you have and from which provider, and what kind of network connectivity devices you're using. /copy Best, Ryan On Mon, Aug 17, 2009 at 3:33 PM, Sean Callahanseancalla...@gmail.com wrote: Hi Ryan, I just replied to your email and also will post here in case you read this first. Maybe others will have an idea too as why basic auth is not working. Long story short - we were down for 3 days, up for the last 3 hours, and now down once again - no one can login using basic auth on our sitehttp://tweetphoto.com. It so happens when I responded to your email about 3 hours ago everything was working fine - meaning I was able to login to TweetPhoto as were other users. Since replying to your second email basic authentication onhttp://tweetphoto.comis not working an no one can login to their account on our domain. I'm not sure why basic auth is not working when you said only OAuth should have been affected. With that said, I have an idea as I've spoken to a few Rackspace customers. Is it possible that a range of IPs at Rackspace are being blocked/throttled preventing users from logging in through basic auth? I'm not sure why basic authentication came back online this morning and now it does not work. You asked me to respond to an email Alex sent, but I have not seen that. Please let me know what information you need to better troubleshoot this issue so we can resume service. As I mentioned in my email to you, I am willing to pay a monthly service fee as I'm sure other Twitter Developers are, to keep service running to TweetPhoto.com up 100% of the time. Please advise. Best Regards, Sean Callahan On Aug 16, 11:40 am, bosher bhellm...@gmail.com wrote: Thanks for the update Chad.. On Aug 16, 10:52 am, Chad Etzel jazzyc...@gmail.com wrote: Hi all, The API team is actively debugging the OAuth issues as we speak. Please be patient as we nail down the problems. Thanks, -Chad On Sun, Aug 16, 2009 at 1:43 PM, Andrew Baderaand...@badera.us wrote: On Sun, Aug 16, 2009 at 1:40 PM, bosherbhellm...@gmail.com wrote: How is it that all the oAuth apps out there are down, but others like TweetMeMe are not? TweetMeMe works just fine, how is that possible? HTTP Basic Auth still works I believe, as do any pre-problem OAuth tokens issued. ∞ Andy Badera ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me:http://www.google.com/search?q=(andrew+badera)+OR+(andy+badera)-Hide quoted text - - Show quoted text -- Hide quoted text - - Show quoted text -
[twitter-dev] Re: Platform downtime is expected
Yeah, no one can login to http://TweetPhoto.com just tried minutes ago and still no dice. Twitter, do I need to provide anything to you or do something on my end to allow users to login through basic authentication on our site? I tried moments ago and could not login, but was able to login to a competitors site no problem. Please advise. -Sean On Aug 15, 8:21 pm, Jonathan George jonat...@jdg.net wrote: 1. It's been roughly 10 hours. How about an update? 2. It'd be great if you would post this to status.twitter.com, in addition to the developer mailing list. Status is seen by more users, and the last update you have on it is rather ambiguous. When users see that the Twitter web interface is up and running, they expect the apps to be up and running as well. best, jonathan On Aug 15, 1:08 pm, Doug Williams d...@twitter.com wrote: Hi all --If you have been monitoring our status blog [1] or been to Twitter.com today you have noticed that we are once again experiencing problems due to external causes. The issues causing the downtime require that we once again take measures to bring the site back online. The first step our operations team must take will likely cause API downtime, especially affecting OAuth. We apologize for the inconvenience and we will work quickly to reduce the impact to the API. We appreciate your patience and I will update you as soon as we know more. Thanks, Doug
[twitter-dev] Re: Platform downtime is expected
Thanks for the update Doug. Users on TweetPhoto are not able to login. I've added an alert notification on our homepage, http://TweetPhoto.com, to make them aware of the issues linking to the Twitter status blog. Will you need our IPs again to whitelist them or are you good to go. Please let me know how I can be of service. -Sean On Aug 15, 12:37 pm, Sam Street sam...@gmail.com wrote: I haven't experienced any downtime or lack of connectivity so far. On Aug 15, 7:16 pm, dougw d...@twitter.com wrote: Looks like I forgot the link to the status blog. [1]http://status.twitter.com/post/163603406/working-on-unexpected-downtime Thanks, Doug On Aug 15, 11:08 am, Doug Williams d...@twitter.com wrote: Hi all --If you have been monitoring our status blog [1] or been to Twitter.com today you have noticed that we are once again experiencing problems due to external causes. The issues causing the downtime require that we once again take measures to bring the site back online. The first step our operations team must take will likely cause API downtime, especially affecting OAuth. We apologize for the inconvenience and we will work quickly to reduce the impact to the API. We appreciate your patience and I will update you as soon as we know more. Thanks, Doug
[twitter-dev] Re: Platform downtime is expected
Thanks for the reply Doug. Any new news? Still not able to login using basic auth on TweetPhoto. Do you have any ETA as to when we'll be restored? On Aug 15, 1:29 pm, Doug Williams d...@twitter.com wrote: Sean,At this time we are monitoring the situation and containing issues as we see them. Let's hold off on restoration requests until things stabilize. Thanks, Doug On Sat, Aug 15, 2009 at 1:17 PM, Sean Callahan seancalla...@gmail.comwrote: Thanks for the update Doug. Users on TweetPhoto are not able to login. I've added an alert notification on our homepage,http://TweetPhoto.com, to make them aware of the issues linking to the Twitter status blog. Will you need our IPs again to whitelist them or are you good to go. Please let me know how I can be of service. -Sean On Aug 15, 12:37 pm, Sam Street sam...@gmail.com wrote: I haven't experienced any downtime or lack of connectivity so far. On Aug 15, 7:16 pm, dougw d...@twitter.com wrote: Looks like I forgot the link to the status blog. [1] http://status.twitter.com/post/163603406/working-on-unexpected-downtime Thanks, Doug On Aug 15, 11:08 am, Doug Williams d...@twitter.com wrote: Hi all --If you have been monitoring our status blog [1] or been to Twitter.com today you have noticed that we are once again experiencing problems due to external causes. The issues causing the downtime require that we once again take measures to bring the site back online. The first step our operations team must take will likely cause API downtime, especially affecting OAuth. We apologize for the inconvenience and we will work quickly to reduce the impact to the API. We appreciate your patience and I will update you as soon as we know more. Thanks, Doug
[twitter-dev] Re: Early developer preview: Retweeting API
I agree with janole. I believe the simple Reply concept would be best in this regard. For example, if I had a tweet that I found, regardless of who its from, I can retweet it, but link together the original tweet in the same manner that we do for the replies. Thus, we create a chain of where a retweeted message came from but also allows us to make comments. Heck, with this direction, you can blow away the original tweet in your tweet and insert a full 140-character comment and with the chain, Twitter can go back to the last tweet in the chain that isn't linked and we can assume this is the original message and display the original above the user's tweet in the timeline, in a similar fashion of how message boards and forums work. On Aug 13, 2:31 pm, janole s...@mobileways.de wrote: Will it be possible to comment on the retweeted tweet? If not, people might just continue to use the current RT ... convention. Retweeting can be a way of acknowledging a tweet or disapproving a tweet etc. If you search for RT in search.twitter.com you'll see a lot of commented retweets. Ole -- @janole / mobileways.de / Gravity
[twitter-dev] OT - Browser Resolution Accessing Twitter.com
Wondering if Twitter Devs would mind sharing what the current 5 top browser resolutions accessing the twitter site? Or if anyone can point me to a secondary source that would be cool Thanks, -- Sean Scott cell: 612.867.8133 portfolio: http://www.flickr.com/photos/92876...@n00/sets/72157613990263453/ profile: http://www.linkedin.com/profile?viewProfile=key=2242610 blog: http://www.twofortyeight.com/ other: http://twitter.com/kalisurfer
[twitter-dev] Seeing same login issues right now as when DDoD happened
I've tried logging into a handful of sites built around the Twitter API without success. I'm seeing the same login issues right now as when the DDoD happened. Twitter is aware of the downtime issue on their status page, http://status.twitter.com, but are they aware of the API issues (e.g., being able to login)? Sean
[twitter-dev] Re: Timeouts and API Errors, Tuesday August 11th
Alex, Did not see this post and posted a new message. Still receiving lots of errors and no one can login on our site, tweetphoto.com, right now along with a handful of others (that I've tried myself). Just wanted to give you a heads up. Thanks! Sean On Aug 11, 1:11 pm, Alex Payne a...@twitter.com wrote: Our operations staff has informed me that the attack ceased several minutes ago. Site performance should be returning to normal. On Tue, Aug 11, 2009 at 12:23, Alex Payne a...@twitter.com wrote: We're currently experiencing another wave of Distributed Denial of Service (DDoS) attacks against our system. Expect periodic slowness and errors until the attack passes or is countered by our operations team and hosting provider. Updates will be provided as we get them. Thanks for your patience. -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x -- Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Basic Authentication is down again on our site
Hi Guys, After the original DDoS attack our service, TweetPhoto.com, was blocked. After communicating my IP addresses an waiting about 48 hours it vegan working Friday afternoon. All of a sudden yesterday afternooon no one could login to our site. I wonder why our site was restored Friday in terms o users being able to login and now yesterday and today no one can login to our site? I tried logging into a couple competitors sites and was able to login without a problem. Can you please help me out a d get my service restored again? Best Regards, Sean Callahan
[twitter-dev] Re: OK Seriously People
Agree with what you said. Very well put. It is affecting most all of us. Our photo sharing service (TweetPhoto) is tied into 20 apps whose users aren't able to upload photo onto our platform. I've communicated by adding an alert to our homepage about the issues which broadcasts the message and hopefully helps manage user expectations. Twitter, you'll figure it out and find a solution. I'm also confident you'll keep us in the loop going foward. Thanks! Sean On Aug 9, 11:05 am, David Fisher tib...@gmail.com wrote: A few of you are acting like real children and a few of you still have your heads screwed on right. I'm confident they are doing everything they can. Chill and enjoy your weekend. They'll get it sorted out. What did you guys do in 2007? Twitter was down all the time then. Your blood pressure must have been through the roof with weekly visits to a shrink if you responded this way every time it went down. dave On Aug 9, 1:48 pm, Neil Ellis neilellis1...@googlemail.com wrote: Nice story Adam, however the band are actually trying to run a business, not doing this for love/free. I can assure you the investors in Twitter will be looking to turn profit. Of course if the band are laid up then the danger is the hotdog man (and all his customers) will go to another band that are still playing and have fans. That's why I'm 100% confident all that can be done is being done, cos plenty of people at Twitter will know how fickle a user base can be. Good luck guys, I know what these situations are like and it's hard on you all - I actually hope you guys are getting some rest because it doesn't sound like this is a 100 yard sprint. I also hope someone is making sure the ops/devs aren't reading this list (or getting emails etc) - stress doesn't help productivity in my experience. Knowing what is at stake does. Again good luck chaps, I know how the trenches feel :-) And of course it does suck for the rest of us too, alas that is business. ATB Neil On 9 Aug 2009, at 18:24, Adam Cloud wrote: ***Scenario*** A band broadcasts their music on a radio station all the time, and people are able to freely tune into it, or go buy their music. They go and play in a city park for free every day just because it's a much nicer experience for the listener then to be just sitting at home listening on their radio. You as an up and coming entrepreneur go buy a hotdog drink stand and setup camp in that park to make some cash off of the flow of people who come to see this free event every day. You being there, giving the ability for people to eat drink without leaving the park allows for more of this bands songs to be heard, in effect increasing the chance that their music might be purchased. So you're essentially helping them, by taking advantage of them for your business. The band gets in a car crash, and alot of equipment is damaged to the point of not being able to be used, along with their main source of transportation. The band starts working to find and replace all that is damaged in their equipment and for their car. Now you can imagine that little hotdog stand guy standing on their doorstep while they recover yelling profanities and how they should be skipping the shipping company who's delivering their parts and get their parts themselves to save time. Yelling that they shouldn't be sleeping, they should be working on their band van right now to make sure it can take them back to the park so he can make some money. People aren't coming to my stand anymore!!! They're going to fast food restaurants and going home. WTF i sold my wife for this stand!!! Now of course, this little hotdog stand man may not have really sold his wife, depending upon which one of you people who are still up in arms about this was put in his place, but i think you get my points. The band could easily move to a venue that has their own hotdog/ drink stand making your services not necessary, but instead of doing that and capitalizing on the profit they could get from that, they're still planning on going back to the same park they do their free shows at, and allowing you to continue earning your money. And this concludes storytime. :) Happy sunday! (Relax!) On Sun, Aug 9, 2009 at 10:58 AM, Terry Jones te...@jon.es wrote: Stuart == Stuart stut...@gmail.com writes: Stuart * I can't believe you lot don't realise that constantly demanding Stuart status updates, while certainly important to you, is little more Stuart than a distraction for those who are actually fighting the good Stuart fight. I woke up this morning with the thought that the Twitter mailing list has now become part of the DDoS. What percentage of the people complaining loudly
[twitter-dev] Re: Twitter Update, 8/9 noon PST
No longer being rate_limited at 150. Back to us being whitelisted. Thanks for the fix. On Aug 9, 12:13 pm, Ryan Sarver rsar...@twitter.com wrote: *Finally* have what we hope is good news for everyone. As of about 10 minutes ago we have been able to restore critical parts of API operation that should have great affect on your apps. As such, most of your apps should begin to function normally again. I have tested a few OAuth apps and they seem to be working as expected. Please test your apps from their standard configs to see what results you get and let us know. I am primarily interested in unexpected throttling and issues with OAuth. I look forward to hearing the results and thanks again for your assistance. Best, Ryan
[twitter-dev] Re: Why is Biz saying things are back in action?
Yeah Jesse, I hear you and am super bummed out. My service, TweetPhoto.com, is also down in terms of users being able to login through basic auth. It's been like that all day. No one has been able to upload photos. I emailed Doug at Twitter and he requested my server's IP address which I provided. I guess they are slowly trying to bring apps back online. I just wish this happened a little sooner. I feel totally helpless at the moment. What are your thoughts? On Aug 6, 6:25 pm, Jesse Stay jesses...@gmail.com wrote: Why is Biz saying things are back in action when apps like mine, and many other very large names are still broken from it. Sending this message to users sends a false message to them stating they should expect we should be up as well. At a very minimum, please state the API is still having issues so users can know what to expect: http://blog.twitter.com/2009/08/update-on-todays-dos-attacks.html Jesse
[twitter-dev] Re: New blocks still happening
Users on our site Jesse provide username and password and still can't login. It has been like that all day. I feel your pain and wish we could get back online quicker. On Aug 6, 6:16 pm, Jesse Stay jesses...@gmail.com wrote: This is also another nick against OAuth. My users can't even log in right now because we're relying on OAuth for login. Jesse On Thu, Aug 6, 2009 at 8:45 PM, Dewald Pretorius dpr...@gmail.com wrote: I have seen the same thing. So, if you have white listed IPs that are still showing a rate limit of 20,000, DO NOT use them right now. After a few minutes of use their rate limits are cut down to 150 per hour. Dewald On Aug 6, 8:58 pm, Tinychat tinycha...@gmail.com wrote: So, like everyone else I was receiving 408's from all our production servers. Wasnt sure what was causing it, but it turned out to be that twitter is blocking the IPs. Ok, must be related to the ddos stuff from earlier on- Must have gotten caught in the crossfire. So I go ahead and use some development servers to start sending requests- All is fine, for about a hour. They are blocked now. So to anyone out there, there is no point using a new IP- It will get blocked within a hour or so. I guess we have to wait for twitters host to fix it, or use actionscript/ajax to have the end user request the data himself (Which is what I am going to do) so its always a unique IP- Hide quoted text - - Show quoted text -
[twitter-dev] Re: Introducing Chad Etzel, Twitter Platform Support
Kudos to you Chad. Keep up the good work! Sean On Jul 31, 4:39 pm, Sam Street sam...@gmail.com wrote: Welcome :) On Jul 31, 9:59 pm, Doug Williams d...@twitter.com wrote: Hi all -- We are excited to announce that Chad Etzel has joined our team part-time to support the developer community. He is the one man show behind TweetGrid [1] amongst other projects [2]. We reached out to Chad to join our team after his continual and valuable participation in the community made his passion for the Platform evident. The Platform team is not the only Twitter team that noticed his value. On a recent trip to our local coffee shop [3], a search engineer shared that Chad often notices search defects and suggests fixes consistently ahead of most other developers. He is one of the most experienced Twitter API developers in the community and we feel this experience will serve developers' interests well. Chad will be helping to answer requests that enter our support channels [3] to bolster our support to developer community. He will be working remotely from his home in North Carolina. You can follow him on Twitter athttp://twitter.com/jazzychad. We are happy to have Chad on our team an look forward to continuing to build support as a pillar of our offering .The API is hiring passionate developers and evangelists so if you are interested in getting involved, please let us know. 1.http://tweetgrid.com 2.http://jazzychad.net 3.http://twitpic.com/a99zj(@noradioand @al3x in frame) Thanks, Doug- Hide quoted text - - Show quoted text -
[twitter-dev] New TweetPhoto Open APIs released - Photo Sharing API (Basic Advanced)
TweetPhoto Open API: http://groups.google.com/group/tweetphoto/web What is included in the Open Photo Sharing API on TweetPhoto: Getting Started with the TweetPhoto API All Write Operations (HTTP POST/PUT/DELETE) Pagination Privileged Operations Basic Upload API (Upload and UploadAndPost) Advanced Upload API (Upload and UploadAndPost) Sample C# Upload and Post Sample iPhone Code for Uploading a Photo Add and Delete User Favorites Add User Comment Add User Photo View Delete User Comment Set User Settings Get Public Stream Photos Get Viewed Photos in Public Stream Get Commented Photos in Public Stream Get Favorite Photos in Public Stream Get User Profile Get User Settings Get Photos Uploaded by a User Get Who Has Viewed a User's Photos or a Specific Photo Get Comments for a User Get Favorites for a User Get Friends for a User Get Photo Details Get Image Paths Embedding Images from Pic.gd URLs Available Atom and RSS Feeds Fetch Image from TweetPhoto URL Signin and Provision
[twitter-dev] TweetPhoto Open API Just Released (Photo Sharing Platform for Twitter)
The TweetPhoto Open API is now available to the Twitter developer community. It is the most expansive photo sharing API available within the Twitter eco-system. You can view the Open API at http://groups.google.com/group/tweetphoto/web Here you can get your API key here http://www.tweetphoto.com/developer.php Please let me know if you have any questions. Best Regards, Sean Callahan
[twitter-dev] Re: Larger Users Not Returning Follower Data
Jesse, If the implementation is to make that a preference which is turned off by default (no DM by non followers) that users can toggle, then i am totally for it. As you point out its then the users responsibility to clean their inboxes if they get hit by spam after turning the feature on. So for what it counts, I'm all in favor allowing DMs from non followers if its a preference users can control. Sean On Thu, Jun 4, 2009 at 10:54 PM, Jesse Stay jesses...@gmail.com wrote: Sean, why not let the users decide that though? If I enable the option for my account it's my responsibility to weed out the spam. If I don't want the spam then I won't enable it on my account. Giving users multiple options is a good thing. Jesse On Thu, Jun 4, 2009 at 2:31 PM, Sean Scott sean@gmail.com wrote: Just speaking from a user perspective, I'd love to see that debate about opening DM to senders who you are not following to the community as a whole or a representative subset of them. By opening DMs to non-followed twitters, it would be way to easy for spammers to start spamming via DMs. From a user perspective i don't see a compelling argument for opening DMS to folks i do not follow. Off my soap box On Thu, Jun 4, 2009 at 3:23 PM, Doug Williams d...@twitter.com wrote: We would like users to be judicious with their following habits and only follow users who contribute value to their timeline. This justifies the following limits we impose. We are aware that many users would like to accept all incoming directs. This, along with the quid pro quo following to build community, capture the majority of the use-cases for auto-following. We are discussing internally how to best approach these two uses within the bounds of the product we are trying to build. At this time we have nothing to report but know we are actively thinking about these ideas. Thanks, Doug On Thu, Jun 4, 2009 at 2:12 AM, Jesse Stay jesses...@gmail.com wrote: Also, how do you recommend we deal with the larger users that would like to follow back their followers? With the hard limit of 1,000 follows per day, there is no way they'll ever catch up, as some of them have more than 1k new followers per day as is. If this limit were more dynamic based on the size of the user that would be nice. Capabilities to follow people in bulk may also help. Of course, I think many of these would no longer need to follow back if they could just have the option to enable anyone to DM them if they choose. I think that's the underlying cause to want to auto-follow for most people. The only other cause is for an additional token/feeling of community, although I think many would be willing to forgo that if they had the ability to just allow everyone to DM them - it feels good to have someone you admire follow you back, even if it's not 100% sincere. Jesse On Thu, Jun 4, 2009 at 3:07 AM, Jesse Stay jesses...@gmail.com wrote: Yes, that's what appears to be happening. My experience starts at around 500K+. I'm okay with waiting with my script if you guys need to take longer to retrieve the info. Or if you'd prefer we paginate I'll start doing that as well. Maybe a hard limit of 200K and you have to Page to get above that? Jesse On Thu, Jun 4, 2009 at 12:26 AM, Doug Williams d...@twitter.comwrote: I've heard that list sizes greater than 150K-200K start to return timeouts at higher rates. Although I'd enjoy hearing first-hand experiences and recommendations. Thanks, Doug On Wed, Jun 3, 2009 at 9:19 PM, Jesse Stay jesses...@gmail.comwrote: In my case specifically it's the Social Graph methods. I didn't realize you had paging available now. Is there some logic as to when I should expect to page and when I can just rely on the full result? Jesse On Wed, Jun 3, 2009 at 9:56 PM, Doug Williams d...@twitter.comwrote: What methods in particular are you referring to? The social graph methods now support paging so retrieving all of that data is now possible, where it used to throw 502s. It does however require a bit of application logic to assume when paging is necessary (e.g. large follower counts). Additionally, we are making changes to the databases which cause latency that result in periodic 502s. We are not able to give definitive ETAs on these fixes due to priorities that change as unforeseeable critical needs arise. More specificity would be beneficial. Do you have a replaceable bug, problem, or suggestion that you would like to discuss? Thanks, Doug On Wed, Jun 3, 2009 at 7:22 PM, Jesse Stay jesses...@gmail.comwrote: I was discussing this with Iain, and have also talked about it with Damon, so I know I'm not alone in this. I am having huge issues retrieving follower and friend data for the larger users (1 million+ followers), most of the time returning 502 Bad Gateway errors. I know there are a few of these users getting really
[twitter-dev] Re: Trending Service for a given set of users
I'm currently building an AIR twitter client (yes i know yet another one) and part of the goal is to help users see what is popular (trending) within their own community. The most popular URLS and topics information exists for twitter at large, but sometimes what happens in your own group of cohorts is more interesting and usefull than knowing that 15 million people are really digging American Idol right now. So looking for most popular URL RT, most popular topic for a given set of users. Bonus if the service can also return the same information for the followers of the user set. Hope that helps On Tue, Apr 14, 2009 at 4:21 PM, Carlos Crosetti carlos.crose...@gmail.comwrote: Please can you explain the trending output you are looking for? On Tue, Apr 14, 2009 at 2:45 PM, kalisurfer sean@gmail.com wrote: Hi All, Looking for a service where provided a list of users (100+) i can get back the trending URL, topics, hash and RT. Love to be able to access the info via a REST API. Trying to not build it out myself. Thanks, Sean @kalisurfer -- Carlos Crosetti -- Sean Scott cell: 612.867.8133 portfolio: http://www.flickr.com/photos/92876...@n00/sets/72157613990263453/ profile: http://www.linkedin.com/profile?viewProfile=key=2242610 blog: http://www.twofortyeight.com/ other: http://twitter.com/kalisurfer
[twitter-dev] Re: Direct message appearing and disappearing on each refresh
I'm assuming the recent disappearing tweets issue is a known bug as well? I filed it anyway, but it seems to be widespread enough to have already attracted attention... On Thu, Mar 19, 2009 at 11:32 AM, benjackson bhjack...@gmail.com wrote: Seems like Twitterfone is fine (I assume it's using different params as it archives locally). Though Tweetie is also FUBAR. On Mar 18, 7:53 pm, Alex Payne a...@twitter.com wrote: Very much so. On Wed, Mar 18, 2009 at 14:43, benjackson bhjack...@gmail.com wrote: We're seeing an issue where the latest direct message is cut out of the list when refreshing, and then included/cut again upon each refresh. Is this a known issue? -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
[twitter-dev] Not appearing in search results
My Twitter feed has been unprotected for all of its existence, but I can't get it to show up in search.twitter.com results. The most obvious example might be the hashtag #wff2009 -- there aren't that many posts out there in all of Twitterdom that feature it, but none of them are mine. I'm hoping to use Twitter for business communication purposes in the future, but those plans rely on being able to trust that searches I do on a given hashtag actually find all the responses. Any ideas? My feed it twitter.com/traineenews Thanks.
[twitter-dev] Re: Freelance Twitter API Dev directory?
I'd love to be mentioned! Count me in too! Username: @twobile URL: http://www.infinitumsoftware.com/twobile Email: spa...@infinitumsoftware.com Author of Twobile Technology: C# on Windows Mobile devices Thanks! On Feb 23, 11:33 am, Alex Payne a...@twitter.com wrote: There isn't one that I'm aware of, but if people would like to post their contact info in this thread (Twitter username, URL, email, whatever) I'm happy to collect them on the API Wiki. On Sat, Feb 21, 2009 at 18:00, Chad Etzel jazzyc...@gmail.com wrote: Hi All, I have been getting a few requests here and there for twitter API development work. I cannot take on any such projects at the moment, but I always feel bad for leaving them in the lurch. Is there a list or directory anywhere of Twitter API developers that work freelance that I can send to them when this happens? I'm happy to forward on such requests. -Chad -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
Re: Problems with updating profile image
For any one interested, here is a completed function.
public static void UploadProfileImage(byte[] photo, string username,
string pwd)
{
//photo is just a byte array of the image data
//A recent change to Twitter's api requires this line to
be included for .NET clients because
//of how the HttpWebRequest object formats the header. I
had to set this in the new for my class, it
//seemed to be too late if I set it in this function.
You'll get a 417 error without setting this.
// System.Net.ServicePointManager.Expect100Continue =
false;
HttpWebRequest request = (HttpWebRequest)
HttpWebRequest.Create(@http://twitter.com/account/
update_profile_image.xml);
request.PreAuthenticate = true;
request.AllowWriteStreamBuffering = true;
string boundary = System.Guid.NewGuid().ToString();
request.Credentials = new NetworkCredential(username,
pwd);
request.ContentType = string.Format(multipart/form-data;
boundary={0}, boundary);
request.Method = POST;
// Build Contents for Post
string header = -- + boundary;
string footer = -- + boundary + --;
StringBuilder contents = new StringBuilder();
// Image
contents.AppendLine(header);
contents.AppendLine(string.Format(Content-Disposition:
form-data); name=\image\); filename=\{0}\,
twitterProfilePhoto.jpg));
contents.AppendLine(Content-Type: image/jpeg);
contents.AppendLine();
contents.AppendLine(System.Text.Encoding.GetEncoding
(iso-8859-1).GetString(photo));
// Footer
contents.AppendLine(footer);
// Data that is sent with the post
byte[] bytes = Encoding.GetEncoding(iso-8859-1).GetBytes
(contents.ToString());
request.ContentLength = bytes.Length;
using (Stream requestStream = request.GetRequestStream())
{
requestStream.Write(bytes, 0, bytes.Length);
requestStream.Flush();
requestStream.Close();
using (WebResponse response = request.GetResponse())
{
using (StreamReader reader = new
StreamReader(response.GetResponseStream()))
{
string s = reader.ReadToEnd();
}
}
}
}
On Dec 9 2008, 9:50 am, Sean sean.er...@gmail.com wrote:
Thanks Lien.
I was able to get this figured out. It was a problem with the way I
was encoding the image data. I needed to be using iso-8859-1.
I really appreciate your help
On Dec 8, 5:00 pm,Seansean.er...@gmail.com wrote:
Thanks Lien,
I am trying to get this done using c#.NET and I think I am getting
closer. What is happening with my request is it is getting truncated
only a few characters in to the actualimagedata so I don't have a
footer boundary. The post completes successfully, but theimagethat
gets uploaded to the server isn't formatted correctly.
Here is the full request body -
POST /account/update_profile_image.xml HTTP/1.1
Content-Type: multipart/form-data;
boundary=125e2d3d-97d3-44fc-8267-9a8ef2d79644
Authorization: Basic removed
Host:twitter.com
Content-Length: 201010
Expect: 100-continue
--125e2d3d-97d3-44fc-8267-9a8ef2d79644
Content-Disposition: form-data; name=image; filename=seantest.jpg
Content-Type:image/jpeg
ÿØÿà
Any ideas what could be causing theimagedata to be truncated?
Thanks again for your help
On Dec 8, 3:24 pm, Lien Tran lientra...@gmail.com wrote:
Here's what my request body looks like:
POST /account/update_profile_image.xml HTTP/1.1
Authorization: Basic removed
Content-Type: multipart/form-data;
boundary=-1228771270538
User-Agent: Java/1.6.0_02
Host:twitter.com
Accept: text/html,image/gif,image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
Content-Length: 71380
---1228771270538
Content-Disposition: form-data; name=image; filename=Sunset.jpg
Content-Type:image/jpeg
binary data here
---1228771270538--HTTP/1.1 200 OK
On Dec 8, 8:11 am,Seansean.er...@gmail.com wrote:
Would you mind posting a sample of your correctly formatted request
here? I am running windows and haven't been able to get curl up and
running yet.
Thanks
Sean
On Dec 8, 12:06 am, Lien Tran lientra...@gmail.com wrote:
Thanks Alex. I used curl to see what the request should look like and
then coded up my request accordingly. It's working for me now.
On Dec 6, 11:37 am, Alex Payne a...@twitter.com wrote:
The test we use for this method is to use curl:
curl -F 'ima...@path/to/test/image.jpg' -u
USERNAME:PASSWORDhttp
Re: Problems with updating profile image
Thanks Lien. I was able to get this figured out. It was a problem with the way I was encoding the image data. I needed to be using iso-8859-1. I really appreciate your help On Dec 8, 5:00 pm, Sean [EMAIL PROTECTED] wrote: Thanks Lien, I am trying to get this done using c#.NET and I think I am getting closer. What is happening with my request is it is getting truncated only a few characters in to the actualimagedata so I don't have a footer boundary. The post completes successfully, but theimagethat gets uploaded to the server isn't formatted correctly. Here is the full request body - POST /account/update_profile_image.xml HTTP/1.1 Content-Type: multipart/form-data; boundary=125e2d3d-97d3-44fc-8267-9a8ef2d79644 Authorization: Basic removed Host: twitter.com Content-Length: 201010 Expect: 100-continue --125e2d3d-97d3-44fc-8267-9a8ef2d79644 Content-Disposition: form-data; name=image; filename=seantest.jpg Content-Type:image/jpeg ÿØÿà Any ideas what could be causing theimagedata to be truncated? Thanks again for your help On Dec 8, 3:24 pm, Lien Tran [EMAIL PROTECTED] wrote: Here's what my request body looks like: POST /account/update_profile_image.xml HTTP/1.1 Authorization: Basic removed Content-Type: multipart/form-data; boundary=-1228771270538 User-Agent: Java/1.6.0_02 Host: twitter.com Accept: text/html,image/gif,image/jpeg, *; q=.2, */*; q=.2 Connection: keep-alive Content-Length: 71380 ---1228771270538 Content-Disposition: form-data; name=image; filename=Sunset.jpg Content-Type:image/jpeg binary data here ---1228771270538--HTTP/1.1 200 OK On Dec 8, 8:11 am, Sean [EMAIL PROTECTED] wrote: Would you mind posting a sample of your correctly formatted request here? I am running windows and haven't been able to get curl up and running yet. Thanks Sean On Dec 8, 12:06 am, Lien Tran [EMAIL PROTECTED] wrote: Thanks Alex. I used curl to see what the request should look like and then coded up my request accordingly. It's working for me now. On Dec 6, 11:37 am, Alex Payne [EMAIL PROTECTED] wrote: The test we use for this method is to use curl: curl -F '[EMAIL PROTECTED]/to/test/image.jpg' -u USERNAME:PASSWORDhttp://twitter.com/account/update_profile_image.xml If you use an HTTP proxy, you can see it generating the appropriate request and response. On Sat, Dec 6, 2008 at 00:09, Lien Tran [EMAIL PROTECTED] wrote: Hello, I've been trying to update myprofileimageusing the account method update_profile_image. However, the server keeps returning the error There was a problem with your picture. Probably too big. The photo I am trying touploadis a jpg less than 700 kilobytes in size. Below is the request body and request response. Request body: POST /account/update_profile_image.xml HTTP/1.1 Authorization: Basic encoded credentials here User-Agent: Jakarta Commons-HttpClient/3.1 Host: twitter.com Content-Length: 71440 Content-Type: multipart/form-data; boundary=tUGDGHg6- mbUEjVXYFhFWeb_NFmBUxiXOK --tUGDGHg6-mbUEjVXYFhFWeb_NFmBUxiXOK Content-Disposition: form-data; name=Sunset.jpg; filename=Sunset.jpg Content-Type: application/octet-stream; charset=ISO-8859-1 Content-Transfer-Encoding: binary binary data here --tUGDGHg6-mbUEjVXYFhFWeb_NFmBUxiXOK-- Response body: HTTP/1.1 403 Forbidden Date: Sat, 06 Dec 2008 07:59:53 GMT Server: hi Last-Modified: Sat, 06 Dec 2008 07:59:53 GMT Status: 403 Forbidden Pragma: no-cache Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Content-Type: application/xml; charset=utf-8 Content-Length: 183 Expires: Tue, 31 Mar 1981 05:00:00 GMT Set-Cookie: _twitter_sess=BAh7BzoHaWQiJWRhOWNmNjI1MGM5MjRmYWIwOGEzOGQwNTQyYzNmZTNjIgpm %250AbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAG %250AOgpAdXNlZHsA--d9fe4dcadf2064553d3371c9fe767ff009f20c21; domain=.twitter.com; path=/ Vary: Accept-Encoding Connection: close ?xml version=1.0 encoding=UTF-8? hash request/account/update_profile_image.xml/request errorThere was a problem with your picture. Probably too big./ error /hash Does the request body look correct? Does anyone have a sample of what the request body should look like if this is not correct? Thanks. -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x-Hidequotedtext - - Show quoted text -- Hide quoted text - - Show quoted text -- Hide quoted text - - Show quoted text -
Re: Problems with updating profile image
Thanks Lien, I am trying to get this done using c#.NET and I think I am getting closer. What is happening with my request is it is getting truncated only a few characters in to the actual image data so I don't have a footer boundary. The post completes successfully, but the image that gets uploaded to the server isn't formatted correctly. Here is the full request body - POST /account/update_profile_image.xml HTTP/1.1 Content-Type: multipart/form-data; boundary=125e2d3d-97d3-44fc-8267-9a8ef2d79644 Authorization: Basic removed Host: twitter.com Content-Length: 201010 Expect: 100-continue --125e2d3d-97d3-44fc-8267-9a8ef2d79644 Content-Disposition: form-data; name=image; filename=seantest.jpg Content-Type: image/jpeg ÿØÿà Any ideas what could be causing the image data to be truncated? Thanks again for your help On Dec 8, 3:24 pm, Lien Tran [EMAIL PROTECTED] wrote: Here's what my request body looks like: POST /account/update_profile_image.xml HTTP/1.1 Authorization: Basic removed Content-Type: multipart/form-data; boundary=-1228771270538 User-Agent: Java/1.6.0_02 Host: twitter.com Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Connection: keep-alive Content-Length: 71380 ---1228771270538 Content-Disposition: form-data; name=image; filename=Sunset.jpg Content-Type: image/jpeg binary data here ---1228771270538--HTTP/1.1 200 OK On Dec 8, 8:11 am, Sean [EMAIL PROTECTED] wrote: Would you mind posting a sample of your correctly formatted request here? I am running windows and haven't been able to get curl up and running yet. Thanks Sean On Dec 8, 12:06 am, Lien Tran [EMAIL PROTECTED] wrote: Thanks Alex. I used curl to see what the request should look like and then coded up my request accordingly. It's working for me now. On Dec 6, 11:37 am, Alex Payne [EMAIL PROTECTED] wrote: The test we use for this method is to use curl: curl -F '[EMAIL PROTECTED]/to/test/image.jpg' -u USERNAME:PASSWORDhttp://twitter.com/account/update_profile_image.xml If you use an HTTP proxy, you can see it generating the appropriate request and response. On Sat, Dec 6, 2008 at 00:09, Lien Tran [EMAIL PROTECTED] wrote: Hello, I've been trying to update myprofileimageusing the account method update_profile_image. However, the server keeps returning the error There was a problem with your picture. Probably too big. The photo I am trying touploadis a jpg less than 700 kilobytes in size. Below is the request body and request response. Request body: POST /account/update_profile_image.xml HTTP/1.1 Authorization: Basic encoded credentials here User-Agent: Jakarta Commons-HttpClient/3.1 Host: twitter.com Content-Length: 71440 Content-Type: multipart/form-data; boundary=tUGDGHg6- mbUEjVXYFhFWeb_NFmBUxiXOK --tUGDGHg6-mbUEjVXYFhFWeb_NFmBUxiXOK Content-Disposition: form-data; name=Sunset.jpg; filename=Sunset.jpg Content-Type: application/octet-stream; charset=ISO-8859-1 Content-Transfer-Encoding: binary binary data here --tUGDGHg6-mbUEjVXYFhFWeb_NFmBUxiXOK-- Response body: HTTP/1.1 403 Forbidden Date: Sat, 06 Dec 2008 07:59:53 GMT Server: hi Last-Modified: Sat, 06 Dec 2008 07:59:53 GMT Status: 403 Forbidden Pragma: no-cache Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Content-Type: application/xml; charset=utf-8 Content-Length: 183 Expires: Tue, 31 Mar 1981 05:00:00 GMT Set-Cookie: _twitter_sess=BAh7BzoHaWQiJWRhOWNmNjI1MGM5MjRmYWIwOGEzOGQwNTQyYzNmZTNjIgpm %250AbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAG %250AOgpAdXNlZHsA--d9fe4dcadf2064553d3371c9fe767ff009f20c21; domain=.twitter.com; path=/ Vary: Accept-Encoding Connection: close ?xml version=1.0 encoding=UTF-8? hash request/account/update_profile_image.xml/request errorThere was a problem with your picture. Probably too big./ error /hash Does the request body look correct? Does anyone have a sample of what the request body should look like if this is not correct? Thanks. -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x-Hidequoted text - - Show quoted text -- Hide quoted text - - Show quoted text -
Re: Problems with updating profile image
Thanks Lien, I am trying to get this done using c#.NET and I think I am getting closer. What is happening with my request is it is getting truncated only a few characters in to the actual image data so I don't have a footer boundary. The post completes successfully, but the image that gets uploaded to the server isn't formatted correctly. Here is the full request body - POST /account/update_profile_image.xml HTTP/1.1 Content-Type: multipart/form-data; boundary=125e2d3d-97d3-44fc-8267-9a8ef2d79644 Authorization: Basic removed Host: twitter.com Content-Length: 201010 Expect: 100-continue --125e2d3d-97d3-44fc-8267-9a8ef2d79644 Content-Disposition: form-data; name=image; filename=seantest.jpg Content-Type: image/jpeg ÿØÿà Any ideas what could be causing the image data to be truncated? Thanks again for your help On Dec 8, 3:24 pm, Lien Tran [EMAIL PROTECTED] wrote: Here's what my request body looks like: POST /account/update_profile_image.xml HTTP/1.1 Authorization: Basic removed Content-Type: multipart/form-data; boundary=-1228771270538 User-Agent: Java/1.6.0_02 Host: twitter.com Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Connection: keep-alive Content-Length: 71380 ---1228771270538 Content-Disposition: form-data; name=image; filename=Sunset.jpg Content-Type: image/jpeg binary data here ---1228771270538--HTTP/1.1 200 OK On Dec 8, 8:11 am, Sean [EMAIL PROTECTED] wrote: Would you mind posting a sample of your correctly formatted request here? I am running windows and haven't been able to get curl up and running yet. Thanks Sean On Dec 8, 12:06 am, Lien Tran [EMAIL PROTECTED] wrote: Thanks Alex. I used curl to see what the request should look like and then coded up my request accordingly. It's working for me now. On Dec 6, 11:37 am, Alex Payne [EMAIL PROTECTED] wrote: The test we use for this method is to use curl: curl -F '[EMAIL PROTECTED]/to/test/image.jpg' -u USERNAME:PASSWORDhttp://twitter.com/account/update_profile_image.xml If you use an HTTP proxy, you can see it generating the appropriate request and response. On Sat, Dec 6, 2008 at 00:09, Lien Tran [EMAIL PROTECTED] wrote: Hello, I've been trying to update myprofileimageusing the account method update_profile_image. However, the server keeps returning the error There was a problem with your picture. Probably too big. The photo I am trying touploadis a jpg less than 700 kilobytes in size. Below is the request body and request response. Request body: POST /account/update_profile_image.xml HTTP/1.1 Authorization: Basic encoded credentials here User-Agent: Jakarta Commons-HttpClient/3.1 Host: twitter.com Content-Length: 71440 Content-Type: multipart/form-data; boundary=tUGDGHg6- mbUEjVXYFhFWeb_NFmBUxiXOK --tUGDGHg6-mbUEjVXYFhFWeb_NFmBUxiXOK Content-Disposition: form-data; name=Sunset.jpg; filename=Sunset.jpg Content-Type: application/octet-stream; charset=ISO-8859-1 Content-Transfer-Encoding: binary binary data here --tUGDGHg6-mbUEjVXYFhFWeb_NFmBUxiXOK-- Response body: HTTP/1.1 403 Forbidden Date: Sat, 06 Dec 2008 07:59:53 GMT Server: hi Last-Modified: Sat, 06 Dec 2008 07:59:53 GMT Status: 403 Forbidden Pragma: no-cache Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Content-Type: application/xml; charset=utf-8 Content-Length: 183 Expires: Tue, 31 Mar 1981 05:00:00 GMT Set-Cookie: _twitter_sess=BAh7BzoHaWQiJWRhOWNmNjI1MGM5MjRmYWIwOGEzOGQwNTQyYzNmZTNjIgpm %250AbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAG %250AOgpAdXNlZHsA--d9fe4dcadf2064553d3371c9fe767ff009f20c21; domain=.twitter.com; path=/ Vary: Accept-Encoding Connection: close ?xml version=1.0 encoding=UTF-8? hash request/account/update_profile_image.xml/request errorThere was a problem with your picture. Probably too big./ error /hash Does the request body look correct? Does anyone have a sample of what the request body should look like if this is not correct? Thanks. -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x-Hidequoted text - - Show quoted text -- Hide quoted text - - Show quoted text - --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Twitter Development Talk group. To post to this group, send email to twitter-development-talk@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/twitter-development-talk?hl=en -~--~~~~--~~--~--~---
Update profile image
I have been trying for a while to get the update_profile_image method
to work without much luck. I have been able to successfully call
several other methods including ./friendships/create/ and account/
verify_credentials.xml, but have been having trouble with this method.
The exception returned is: The remote server returned an error: (403)
Forbidden.
And the status on the exception is: ProtocolError
I have verified that the image I am trying to upload will upload using
the settings page on my Twitter account. It is a 30x30 jpg.
I am using c# and the HttpWebRequest class. I am sure there is a
problem with how I am generating the multi-part form data because if I
change the name of the image parameter I get the same message which
I think means the service can't parse the request data the way I am
sending it.
Code is below along with the error message and response object I get
back from the server. If anyone has any ideas about what I am doing
wrong I would really appreciate the help. Thanks.
Code:
private void UploadFile(string filename)
{
string url = @http://twitter.com/account/
update_profile_image.xml;
HttpWebRequest request = (HttpWebRequest)WebRequest.Create
(url);
string boundary = 7d72b92a170f1a;
string headerBoundary = --7d72b92a170f1a; //
two dashes less than boundary
string newline = \r\n;
request.ContentType = multipart/form-data; boundary= +
headerBoundary;
request.Method = POST;
MemoryStream data = new MemoryStream();
StreamWriter sw = new StreamWriter(data);
sw.Write(boundary + newline);
// Write file to data
sw.Write(Content-Disposition: form-data; name=\image\;
image=\{0}\{1}, filename, newline);
sw.Flush();
byte[] file = File.ReadAllBytes(filename);
data.Write(file, 0, file.Length);
sw.Write(newline);
sw.Write(newline);
sw.Write({0}--{1}, boundary, newline);
sw.Flush();
// write data to request
request.ContentLength = data.Length;
request.Headers.Add(Authorization, Basic +
System.Convert.ToBase64String(System.Text.Encoding.UTF8.GetBytes
(username:password)));
using (Stream s = request.GetRequestStream())
{
data.WriteTo(s);
}
data.Close();
try
{
// use the request object to get to the response
WebResponse response = request.GetResponse();
if (response != null)
{
StreamReader sr = new StreamReader
(response.GetResponseStream());
string result = sr.ReadToEnd();
}
}
catch (WebException exception)
{
HttpWebResponse httpResponse = (HttpWebResponse)
exception.Response;
}
}
Exception and response details:
CharacterSetutf-8
ContentEncoding
ContentLength 183
ContentType application/xml; charset=utf-8
Cookies {System.Net.CookieCollection}
Headers {Status: 403 Forbidden
Pragma: no-cache
Vary: Accept-Encoding
Connection: close
Content-Length: 183
Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-
check=0
Content-Type: application/xml; charset=utf-8
Date: Fri, 05 Dec 2008 15:26:28 GMT
Expires: Tue, 31 Mar 1981 05:00:00 GMT
Last-Modified: Fri, 05 Dec 2008 15:26:28 GMT
Set-Cookie:
_twitter_sess=BAh7BzoHaWQiJTgxZmIyODE1ZjY3MGI3YjRiOGE1MmFkODJmNjhlOGQwIgpm
%250AbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAG
%250AOgpAdXNlZHsA--b336ca8846bc144106c5160724c82d54b2bfe824;
domain=.twitter.com; path=/
Server: hi
System.Net.WebHeaderCollection
IsMutuallyAuthenticated FALSE
LastModified{12/5/2008 9:26:28 AM}
Method POST
ProtocolVersion {1.1}
ResponseUri {http://twitter.com/account/update_profile_image.xml}
Server hi
StatusCode Forbidden
StatusDescription Forbidden
ExceptionStatus ProtocolError
