[twitter-dev] NSURLConnection
Any opinions on which approach is better.
NSData *data = [NSURLConnection sendSynchronousRequest:request
returningResponse:response
error:error];
OR
connectionInProgress=[[NSURLConnection alloc]initWithRequest:request
delegate:self
startImmediately:YES];
}
- (void)connection:(NSURLConnection *)connection didReceiveData:
(NSData *)data{
}
- (void)connection:(NSURLConnection *)connection didFailWithError:
(NSError *)error{
}
- (void)connectionDidFinishLoading:(NSURLConnection *)connection{
}
--
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] Twitter API changes
Hello, Recently twitter has changed the access level that apps are getting to the user detail, an app need to mark that it needs access to the user's DMs in order to get it (unlike before), i have marked this option in my app settings page on twitter so i will have full data access for new users registering to my app. my question is what about users who performed authentication before that change? will i still be getting full access to their account (including DMs)? are there any other issues in the api change that might restrict the data im getting from twitter? Thanks! Ran -- 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] OAuth IP Change Limited?
I registed a Twitter application, and deployed with my website on a VPS run very well. When I chaged another VPS with new IP to deploy it, I got error within oauth process: *OAuth::Unauthorized (401 Unauthorized):* * * After I change back with old IP, it's good again. The register application domain bind with IP? Meaglith Ma --- Twitter: http://twitter.com/startuplabing Website: http://start-up.im --- -- 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] How do I get top tweets for certain hashtags to my websites?
I want to make a website (my first project) that pulls the top tweets on twitter that are related to wisdom quotes and I want to put them into my website, one quote a day. I want to enable visitors to subscribe to get those quotes by email, sms, facebook updates, tweets on their accounts too. So, basically, I want to know what will I need to know to do this project. I would really appreciate any feedbacks. -- 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] NSURLConnection
I am pretty sure you don’t want to use any synchronous requests, though.
Better make an asynchronous one, and handle delegate method callbacks when they
finish. Otherwise, if network flakes out, it can easily clog up everything for
a minute or so, plus it’s just bad to write network code that works
synchronously. :)
-ev
On Jun 27, 2011, at 00:36, R wrote:
Any opinions on which approach is better.
NSData *data = [NSURLConnection sendSynchronousRequest:request
returningResponse:response
error:error];
OR
connectionInProgress=[[NSURLConnection alloc]initWithRequest:request
delegate:self
startImmediately:YES];
}
- (void)connection:(NSURLConnection *)connection didReceiveData:
(NSData *)data{
}
- (void)connection:(NSURLConnection *)connection didFailWithError:
(NSError *)error{
}
- (void)connectionDidFinishLoading:(NSURLConnection *)connection{
}
--
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] Public Time-Line Rate Limiting
I am working on my dissertation to apply DM algorithms on public tweets. I wrote a Java application to grab the public timeline in xml format. My intention was to make the request from the Java thread after every 6 milliseconds (1 minute) to get a bunch of tweets for my dataset. But I missed one zero! I got the rate limiting error: Server returned HTTP response code: 400 for URL: http://twitter.com/statuses/public_timeline.xml; just a few moments into my first run. Is my IP banned forever to make the public time line request? How can i be whitelisted again? Thanks -- 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] How to remove a tweet by URL
Hi.
I search how to remove a tweet with an URL with no success.
I saw in github this code:
$method = statuses/destroy/{$status-id};
twitteroauth_row($method, $connection-delete($method), $connection-
http_code);
So I made my url like this:
http://twitter.com/statuses/destroy/maxo_geek/85075493296144384
(( http://twitter.com/statuses/destroy/'.$screen_name.'/'.tweet_id.'
))
But it doesn't work.
Any ideas ?
Thanks
Ps: sorry for my bad english, I'm french.
--
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] Access tokens changing on their own?
Then something is definitely broken; because I have not changed anything but the access tokens keep changing. Taylor? Matt? Arnaud? Thanks... Nick On 6/26/2011 1:50 AM, Scott Wilcox wrote: They'll only change when you reset your consumer key/secret and perhaps your account password too. On 26 Jun 2011, at 06:49, Nicholas Chase wrote: This happened to me again today. Am I the only one it's happening to? Nick On 6/24/2011 10:24 PM, Nicholas Chase wrote: Today, for the second or third time in a couple of months, my application access tokens seem to have changed on their own. My app was working fine, and then all of a sudden I started getting authentication errors. I went and checked, and my access tokens had changed. Do they change regularly? They they change when I access a particular page or something? Nick -- Scott Wilcox @dordotky | sc...@dor.ky mailto:sc...@dor.ky | http://dor.ky +44 (0) 7538 842418 | +1 (646) 827-0580 -- 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 https://groups.google.com/forum/#%21forum/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] Re: A few updates about the permission model change
Hi Matt, We missed the bit about having to use oauth/authorize and were going through oauth/authenticate. Via oauth/authorize it's working properly. Aaron On Jun 23, 6:57 pm, Matt Harris thematthar...@twitter.com wrote: Hi Aaron, I have't been able to reproduce this issue so could you email me details of the app and captures of the requests and responses. Then I can investigate further. Thanks, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Wed, Jun 22, 2011 at 12:57 PM, Aaron Rankin aran...@sproutsocial.comwrote: Hi Matt / Twitter, We're not seeing the Direct Message permission setting ever take effect. In our application profile, it says that we're set to request read, write and DM, and we've saved this several times successfully. However, both the X-Access-Level header and the oauth/authorize page list that we don't have DM access (and for the former, on accounts for which we've re-authorized). Aaron On Jun 13, 7:56 pm, Matt Harris thematthar...@twitter.com wrote: Hey everyone, A number of updates were made to the Direct Message methods and OAuth screens at the end of last week. Here's what went out: * force_login is now supported onhttps://api.twitter.com/oauth/authorize * the OAuth screens now support a feature phone tier of handsets and render them in a simpler format * the language on all the screens is standardized to say direct message * there is a Return to App URL on the Deny and Cancel screens that redirects the user to the oauth_callback url with a 'denied' parameter instead of oauth_token. This next parameter isn't needed by everybody but we will be adding screen_name support to the authorize and authenticate pages in the next few days. If you want to add this to your code ready for when we release the feature you can, but please know the screen_name parameter will be ignored unless you also provide the force_login parameter. The screen_name parameter pre-fills the username field of the OAuth screen when force_login is true. The user is still able to edit the field, even if it is prefilled. Lastly, these are the main points discussed in previous emails and Tweets: * The new permission level will be enforced on 30th June. * If you don't need to read or delete direct messages you do not need to update the permission level of your application. * Read/Write applications will still be able to send direct messages, even after the enforcement date. * Existing oauth_tokens will not be invalidated, even if the application permission level is altered. * You can find out the current permission level of an oauth_token by inspecting the headers of an authenticated request to the API. Look for the X-Access-Level header. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter -- 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] Re: Twitter API error on my website
The Twitter API returned an error while processing your request. Please try again. Are you using a widget or you are using some custom code for feeding the tweets in your wordpress website? If you are using some widget, then most probably it will start working again after some time. Mohan -- 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] Twitter API changes
hi, the users who are already logged in should logout and relogin againotherswise they will not get any data(not only DM's) because u chaged the application settings(i found this issues in my app) //kamesh On Sun, Jun 26, 2011 at 6:42 PM, Ran Margaliot ran5...@gmail.com wrote: Hello, Recently twitter has changed the access level that apps are getting to the user detail, an app need to mark that it needs access to the user's DMs in order to get it (unlike before), i have marked this option in my app settings page on twitter so i will have full data access for new users registering to my app. my question is what about users who performed authentication before that change? will i still be getting full access to their account (including DMs)? are there any other issues in the api change that might restrict the data im getting from twitter? Thanks! Ran -- 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] GET statuses/retweets/:id
The documentation at http://dev.twitter.com/doc/get/statuses/retweets/:id states it will return up to 100 of the first retweets of a given tweet. However, in practice the method seems to only return the recent Retweets for a given Tweet. Take these two urls: http://www.flickfolia.com/free shows 17 Retweets. This url is using the api to return Retweets. http://twitter.com/#!/Flickfolia/status/85127683410886656 shows that there has been 29 Retweets. Note: The stats are as of the time of this post. -- 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 statuses/retweets/:id
Ah, ok. Seems you need to specify count param to be accurate. On Jun 26, 10:22 pm, Chris Teso christ...@gmail.com wrote: The documentation athttp://dev.twitter.com/doc/get/statuses/retweets/:id states it will return up to 100 of the first retweets of a given tweet. However, in practice the method seems to only return the recent Retweets for a given Tweet. Take these two urls:http://www.flickfolia.com/freeshows 17 Retweets. This url is using the api to return Retweets.http://twitter.com/#!/Flickfolia/status/85127683410886656shows that there has been 29 Retweets. Note: The stats are as of the time of this post. -- 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
