Discussing API v1.1

[devbeez]

I’ve been wondering if there is a way in 1.1 to directly get a list of friends who are in a “bi-directional” friendship relation with a selected user.
Right now I have to get a list of people the specified user is following with “friends/ids.json” and then check each one if they are also following the specified user with “friendships/lookup.json”.
It’s a very cumbersome method and it would be nice if I could get the list with a single command.

[episod]

There’s no such direct method. However, there’s a much simpler approach and that’s comparing the output from friends/ids to the output of followers/ids. Where intersection exists, so also does a mutual following relationship.

[sferik]

If a user has only authorized an application for read-only access, POST will fail. I’m not sure if this behavior is intentional. It seems like POST should be allowed in read-only applications, since no data is being written.

[devbeez]

That could also work, but the problem is that getting a list of followers is also subjected to request limitation and I’m guessing there is a much bigger chance I would hit the limit with “followers/ids” than I would with “friendships/lookup”.
Maybe I could mix both methods, but it would still be nice if a more direct solution could be implemented.

[episod]

Hitting the limits shouldn’t be something you’re perpetually trying to avoid. You should scope the work you have to do within what’s possible within the limits and the methods available to you. Some actions may take longer than 15 minutes to accomplish on behalf of a user.

[neconeco64]

I’d like for the public API to get tweets related to some tweets, that do not have any plans?

[JaimeCard]

I’ve switched most of my code from 1.0 to 1.1 however there are 3 endpoints that work fine with 1.0 but with 1.1 I get the following returned…
{
errors = (
{
code = 215;
message = “Bad Authentication data”;
}
);
}

the endpoints not working are…

https://api.twitter.com/1.1/users/suggestions.json
https://api.twitter.com/1.1/users/lookup.json
https://api.twitter.com/1.1/trends/available.json

I am using iOS 6’s SLRequest structure to GET the data and it’s working fine with all other endpoints so I’m totally lost as to why these 3 are failing.

Any ideas what’s going on here? why do these endpoints return a 215 error when the same code works fine for all other endpoints?

[episod]

users/lookup may have to do with comma encoding (potentially using “,” instead of “%25” but the others… that’s strange. Are you passing any parameters to the methods? What does your invocation look like?

[JaimeCard]

Checked my code and would you believe it I’d omitted the authentication on suggestions & available, only spotted it when I went looking for parameters so thanks for that, they now work.

As for the comma encoding I’m using the following code to get the comma separated list of usernames…
int index;

NSString *screenNames = [[savedACUsersList objectAtIndex:0] valueForKey:@"username"]; 

for (index = 1; index < savedACUsersList.count; index++) 
{
	NSString *screenName = [[savedACUsersList objectAtIndex:index] valueForKey:@"username"];
    
    screenNames = [screenNames stringByAppendingFormat:@",%@",screenName];
}</code>  

It works with 1.0 but not 1.1 and I’m definitely authenticating this time.

[JaimeCard]

Turned out not to be the commas after all, I was passing a null account to the endpoint, all fixed and working now.

[episod]

The profile banner upload and remove API is now available in API v1.1:

• [node:12460]
• [node:12459]

Additionally, we’ve added a convenience method for those who are not fans of string manipulation:

• [node:12461]

[neconeco64]

The /application/rate_limit_status method, I want to be able to get a rate-limiting information statuses/update_status_with_media.

[beeclass]

Is it correct?
When I downloaded 5,000 ids using followers/ids API v 1, each call resulted in duplicated ids except for first one or two ids.

I uploaded a screen capture to describe this problem. http://facstaff.elon.edu/byunglee/politics.png

It happened when I got Santorum’s followers and Romney’s followers.

[beeclass]

Have you called followers/ids multiple times with different next_cursor?
I got duplicated ids except for the first one or two from each of many calls.
I uploaded a screen capture to describe this problem. http://facstaff.elon.edu/byunglee/politics.png
If you have any idea, please let me know also by emailing me at byunglee@gmail.com

[simbeckhampson]

Newbie: Before I begin, I have read this comment thread and clarity is slowly shining through, but around the edges is some blur. I hope someone here can help remove it.

1. Case example. I’ve been using https://api.twitter.com/1/statuses/following_timeline.rss and dlvr.it 's filtering ability to allow simple curation by users. When a followed user uses a specific hashtag on a unique tweet, ie. not a RT, the post will be auto RT’d to another Twitter account - like a master list of the best of content. I tried using this URL:
   https://api.twitter.com/1.1/statuses/home_timeline.json?screen_name=xxx but got an Auth error in dlvr.it (and ifttt.com). How can I preserve this method of curation using 1.1 and services like Dlvr.it and ifttt.com? Is it going to be possible?

2. Case example. I’ve been using https://api.twitter.com/1/favorites.rss to repost as RT’s via ifttt.com to Hootsuite’s Autoschedule option. How do I preserve this method of posting.

Note: I have a developer account and have created a couple of Apps, ie, one that posts from Wordpress to Twitter. But I’m not a coder and I’m now a little lost how the functionality above will (or could) survive. I hope Twitter can provide me with some hope on how to further both these case examples.

If is not going to be possible after March, please advise so I can rethink client usage. Thanks in advance.

[ssh_tunnel]

Thanks Taylor. When you say ‘at this time’, is there hope for a documented method that returns a similar result set in the near future?

[episod]

We don’t have any plans for this on any near-term roadmap. It would be best to operate assuming that it won’t exist.

[nancypiedrola]

Good afternoon

How could implement the sign in mechanism on API 1.1? What libraries should be included? I want to migrate the signature mechanism in some applications. I’ve read topic Implementing Sign in with Twitter but not specified examples with the tools necessary for the implementation.

Regards

[janole]

Thanks for the clarification.

Just one further question: the official Twitter clients and the webpage will lose this feature, too?

[episod]

The methods lists/members and lists/subscribers are both now rate limited at 180 requests per 15 minute window.