[twitter-dev] Retweet API limitations
Hello, I'm developing an application that also includes the retweet feature and I have some questions regarding the use of retweet API calls. In the documentation it says that the method is subject to update limits. http://dev.twitter.com/doc/post/statuses/retweet/:id What does this mean exactly? For example, if I retweet a tweet 50 or 100 times with different user accounts through the API. Is there a maximum amount of retweets that can be done on a tweet via API calls? Should there be a delay between retweet API calls instead of doing the 50 calls in a row? Regards, Freek -- 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] How to use Twitter API
Hi I can`t use Twitter API to dev. Twitter client. Could you tell me some info of Twitter API. Thanks. Aaron. -- 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] is there a way to update statuses more then 100 per semi-hour at all?
greatings people. im using twitter api to update statuses but im getting this after about 100 of them have been posted in 1 hour time period: error: User is over daily status update limit i HAVE to post new tweets say 200 or even 500 per hour. is it possible at all? if yes how can i achieve this? it won't be spam or some kind of inappropriate materials. this is going to be value posts for my readers. i'd like to have this ability really much. thanks. -- 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] Re: Follower analysis without whitelisting breaks limits?
On 21 Feb., 06:50, Orian Marx (@orian) or...@orianmarx.com wrote: I don't know what the current state of this is but it looks like Site Streams will support unfollow events for this purpose:http://groups.google.com/group/twitter-development-talk/browse_thread... From the mentioned thread: I'm only seeing unfollow events where the tracked user is doing the unfollowing. So if only those unfollowings are reported by the stream, that the tracked user is doing himself, I am not able to watch the followers, that he has lost (other followers unfollow the tracked user). That's not sufficient for follower tracking how we do it. Unfortunately no statement from the twitter guys... Cheers. Jo Seibert On Feb 18, 5:11 pm, Jo jseib...@seibert-media.net wrote: It seems as if no one at twitter as an answer or a solution on this. That's bad... Or are they still thinking about it? Cheers. Jo Seibert On 15 Feb., 11:03, Dewald Pretorius dpr...@gmail.com wrote: Thanks Tim. So the point is, we still need to rely on the follower ids list API method if we want to maintain an up to date picture of an account's followers. For larger accounts this becomes impractical with a limit of 350 calls per hour. On Feb 15, 4:13 am, Tim Haines tmhai...@gmail.com wrote: It sends you an event when our subject user follows someone else, unfollows someone else, or when they are followed by someone else. It does not send an event when they are unfollowed by someone else. Tim. On Tue, Feb 15, 2011 at 3:08 AM, Dewald Pretorius dpr...@gmail.com wrote: If I remember correctly, Site Streams sends you a transaction only when the user follows another user (adding to Following). It does not send you a transaction when someone else follows that user (adding to Followers). I don't know if this work the same in User Streams. Clarification by Twitter will be appreciated. On Feb 14, 12:38 pm, David Giamanco dgiama...@gmail.com wrote: I believe the new way to do this is to initially call the REST API to get all of the ids for the first time you process this user. Then you setup a User Stream on the user and process any requests that come in through there. For your uses, if you only show users the differences in follower counts then you don't need the initial call to the REST API to collect all ids. All you need is a count of the ids and then to initiate a User Stream. The User Stream will give you the differences in real time and you can store just the differences, instead of the entire set of ids. David Giamanco -- 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 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] twaud.io api: anyone manage to get it working?
I've tried discussing with the author of twaud.io, but he says he doesn't really have time to look. I've tried sending even a minimal test iPhone app Xcode project to twitter api support, but a week later no response. Our app is xAuth authorized, the app sends the username and password and gets a token, we produce all the intended headers and post up to twaud.io's api as described at twaud.io/api and yet just get the below totally opaque response: response: HTTP/1.1 403 Forbidden / Not Authorized Made sure that the twitter account I used for testing has given both our app and twaud.io read/write authorization. Here's a sample of what I am putting in X-Verify-Credentials- Authorization (which we've tried naming that way and also, per the twaud.io api page, x_verify_credentials_authorization). We've also tried sending the value as either post values or as a request header: OAuth realm=http%3A%2F%2Fapi.twitter.com, oauth_consumer_key=ofEzSNkKNMzu4ANhII5g, oauth_token=123520286-U3RXmbgPPF0i4lDkVBdSCx9MEJhHMu8KvzAyosXI, oauth_signature_method=HMAC-SHA1, oauth_signature=9Z5VMPeL4QoGHCtpiMcUxF%2FPiXI%3D, oauth_timestamp=1297141216, oauth_nonce=A20C6AB4-AAF9-46A5-B1F0-574A5BD3B538, oauth_version=1.0 I would be more than happy to send a minimal Xcode project to anyone who is willing to try running it in the iOS simulator. -- 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] Feedback regarding URL change
I changed the Registered Callback URL and Registered OAuth Callback URL but below the status being sent by api the old URL remains. I double checked the app by changing the Application Icon just to find out that it changed within twitter. So the account is correct. -- 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
Re: [twitter-dev] is there a way to update statuses more then 100 per semi-hour at all?
You can't post more than 127 (?) tweets per 4 hours (that's 1000 per day). This is a limit which can not be raised. Tom On 2/21/11 10:22 AM, John Carver wrote: greatings people. im using twitter api to update statuses but im getting this after about 100 of them have been posted in 1 hour time period: error: User is over daily status update limit i HAVE to post new tweets say 200 or even 500 per hour. is it possible at all? if yes how can i achieve this? it won't be spam or some kind of inappropriate materials. this is going to be value posts for my readers. i'd like to have this ability really much. thanks. -- 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] Profile Image Uploads return 200 OK but do not update
We are seeing a 200 OK when making profile image uploads via the API however the image either does not update or takes a long time to update (over an hour) on Twitter. I presume this is in relation to: http://status.twitter.com/post/3369948143/image-uploads-partially-disabled And: http://status.twitter.com/post/3365838637/cannot-update-profile-images-resolved Could someone confirm what the current status of Profile Image Uploads via the API is / the status of these issues, they have not been updated since Friday. Thanks, Bob Founder Twibbon.com -- 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] Re: User stream and oauth headers
Sorry, my bad. I was signing the request by using the url with query params included, while the library I'm using expects url and params to be passed separately. On Feb 12, 8:19 pm, aitorciki aitorc...@gmail.com wrote: Hi. I'm using python-oauth2 to handle the authentication with the REST and user stream APIs. I'm using the same code to sign the request in both cases, and send the oauth credentials as authentication header. While everything works perfectly with REST requests, I'm getting 401 responses with the user stream ones. The oauth related code is exactly the same, and token and consumers keys and secrets too. If I change to query parameters based oauth, then everything works correctly with the user stream API. Is there any limitation in how oauth data is to be sent to user stream API? I can't find any specific information on how authentication is no be handled with this endpoint. Should the headers approach work just like in the REST API case? Thanks! -- 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
