Discussing API v1.1

kurrik · 2013-07-09T17:29:53.000Z

I’m not too familiar with the Phirehose library, but it seems like TWITTER_CONSUMER_KEY and TWITTER_CONSUMER_SECRET never get used anywhere? They would need to incorporated into the signing process to generate a valid OAuth signature for the API.

froginthevalley · 2013-07-09T17:32:16.000Z

The information in the oAuth tool on dev.twitter.com needs to be updated, it’s on our (long) todo list. Nonetheless, you should use https://api.twitter.com/1.1/statuses/mentions_timeline.json in your application.

fakedeads · 2013-07-10T03:44:57.000Z

The application can’t run because now Twitter API is 1.1.
I have given a task that I modify that aplication which use twitter API 1.0. The application is java. I want convert API 1.0 to API 1.1. I use eclipse but eclipse can’t detect all things which make error.
What parts which I must change ?

Note : I never use twitter API

SparkleLavz · 2013-07-10T11:09:35.000Z

Hi all,
am trying out the twitter api v1.1 ,but whenever am trying to hit the (Twitter-Application-Only-Authentication-OAuth-PHP-master) API , it throws this error
"Resource id #2Http code:0Curl error: SSL certificate problem: unable to get local issuer certificate"
Please anyone help me out from this…

Thanks In Advance

episod · 2013-07-11T15:12:54.000Z

I recommend getting more familiar with the API, as you’ll be able to understand what to change in moving from v1 to v1.1 and better know what you’re getting yourself into. Identify whether you’re using a third party library – if you are, it’s possible there’s a newer version available and that’ll be your best upgrade path. If you aren’t, then you’ll need to verify which response format you were using – if you were using XML, you’re going to have to switch to JSON. You’ll need to use SSL on all requests, and use methods in the domain/path of api.twitter.com/1.1/* – some methods have moved, some no longer exist. OAuth 1.0A and HTTP spec compliance is stricter.

AmnonOwed · 2013-07-12T22:38:00.000Z

Is the Twitter REST API v1.1 as presented via https://dev.twitter.com/docs/api/1.1 and all the respective sub-pages available as a JSON file that contains the methods, resource information, parameters and descriptions? Or is there some undocumented API call that gives me all the possible API methods?

Because I’d like to import all these things into my application through an automated solution, rather than one by one manually type each method from a webpage into my application. Please advise.

amarpreetkalkat · 2013-07-13T09:17:49.000Z

For some time now, the 1.1 Search API has not been returning complete retweets, and is cutting off the tweet text when it is too long. Visibly, it is happening because 'RT @username: ’ gets appended to the retweet and the corresponding no. of characters from the end of the tweet text just get dropped.

I do notice a ‘truncated’ field in the response, but it does not seem to make sense to provide an abruptly truncated tweet (if that is what truncated is for).

The 1.0 API used to provide full reteweets even if the 'RT @username: ’ was appended and the tweet text was long. I remember this problem coming up once then, a few people reported, and it was soon fixed.

Should we file a bug, or what is otherwise the suggested way around in the current scenario.
Thx.

vthinkdev · 2013-07-15T10:24:19.000Z

changing api create problem my mobile app contain twitter feed ,
My issue is:
here http://jsfiddle.net/9kSBz/

is my code for TWITTER API 1
i got the data in json i access all data using

DATA.RESULTS 
this works fine before realesing of twiiter rest API 1.1
but

my code for 1.1 is http://jsfiddle.net/HbEuL/1/
the same this i use in twitter api 1.1 its not working,
so how can i deal with this data…
i use php for OAuth twitter.

***Note: code is not full its for understand the probelm

episod · 2013-07-15T14:55:04.000Z

No, we don’t provide a direct programmatic means to consume the inventory of methods. However, [node:10280] gets you part of the way there with read-based methods. Consider also this WADL definition format that Apigee puts together: https://github.com/apigee/wadl-library

episod · 2013-07-15T14:56:17.000Z

When working with retweets, you should take the text of the tweet itself from the “retweeted_status”'s text node, not the outermost text node. The retweeted_status/text node will contain the original, untruncated text of the tweet that was retweeted.

4enter10 · 2013-07-16T07:39:11.000Z

twitter.php is not working

4enter10 · 2013-07-16T07:40:20.000Z

i can create a consumerkey and token also but didn’t get twitts

AmnonOwed · 2013-07-17T02:41:00.000Z

Thanks for the reply. I’ve seen GET application/rate_limit_status but it’s hardly what I am looking for. The Apigee link contain so much other / incorrect information that it becomes unusable. I have opted to write my own application that parses the Twitter HTML API into a valid JSON file. You can find it here: https://github.com/AmnonOwed/P5_NetworkVisualization

monday3pm · 2013-07-17T16:14:40.000Z

So multiple apps with the same IP address can now have separate limiting counts? That would be great! So for example, 2 apps (X and Y) with the same IP. Within 15 min, X sends 10 requests to user_timeline, and Y sends 20 requests to user_timeline. Then, X still has 190 and Y has 180 requests to be used, right?

All devices in my organization are using the same IP address so my apps were heavily affected by other ones’ apps.

QPCN · 2013-07-19T19:19:26.000Z

I’m trying to retrieve user_timeline but my application keeps on getting “503:The Twitter servers are up, but overloaded with requests. Try again later. message - Over capacity code - 130” After I fetched the timeline for approximately 10 users, I will get this error. I keep on tracking the ratelimit and I am pretty sure that the app did not reach any limit.

wordsuit · 2013-07-21T06:35:52.000Z

Hi, well here is one more rate limit question!

I am a little confused by the rate limit. I saw I can use 15 calls per 15 minutes. Is that per user or for the website?

episod · 2013-07-22T15:10:56.000Z

It depends on context. Each API method has two limits – a limit for per-user use and a limit for per-application use, without a user. Most often, you’ll be using user-based authentication and the per-user limits.

jdizzle_street · 2013-07-22T23:26:03.000Z

I have a question regarding rate limiting of updates which are actually replies to other Tweets.

Assuming you had 1000 {users} such as
@david
@ben
@fred
@…

If 1000 users tweeted this tweet within the same 30 second period:
From: @{user}
Message: @handle hi

Could the twitter user “@handle” programatically reply to all 1000 tweets with “@{user} bye!” , where @{user} = the from handle such as @david, without being rate limited?

This is, in effect a reply to 1000 unique Twitter handles.So, in summary if you were really popular and you had to reply to 1000 friends messaging you in 30 seconds, and you wanted to reply with the same message to all 1000 friends, would this be rate limited considering it would be with a reply conversation thread?

episod · 2013-07-22T23:41:04.000Z

Writes aren’t currently “rate limited” in the same way the API is.

Accounts have allowances for writes. For tweeting, accounts typically can tweet 1,000 times per day. But this amount can’t be used all at once. It’s divided into roaming periods of time, with much smaller allowable chunks per each window. Over the course of 24 hours, you would be able to reply to those 1,000 users.

That said, if you were responding with the same text to each friend… I have no idea what our abuse detection algorithms would “think” about that.

jdizzle_street · 2013-07-23T02:50:57.000Z

Is there a way to increase write allowances for specific accounts?