[twitter-dev] Re: Managing Multiple Users and /account/geo Woes
Any response would help, even something along the lines of this isn't possible. On Dec 17, 11:14 am, cballou ball...@gmail.com wrote: I'm storing access_tokens for a number of users in my application. When I switch from one account to another for management, I run a background AJAX request on account/verify_credentials to determine if the active user is geo enabled (parameter geo_enabled). If the user isn't geo enabled, I open a lightbox asking them if they'd like to turn on location. I then fire off a redirect to /account/geo if they clicked yes so they can enable location. The problem, at this point, is that the user may be logged into Twitter with a different account. Is there any way for me to do some trickery to switch the logged in user on twitter (i.e. you allow force_login on authentication) to ensure they're logged in as the proper user? Perhaps even some handling to determine the currently logged in user and check if it matches the access_token user? The current handling poses a very big drawback to this beautiful geo page when managing multiple accounts. I need a way of ensuring that / account/geo pertains to the proper user (and not some other managed user account). Any help, solutions, workarounds, or suggestions would be much 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] Managing Multiple Users and /account/geo Woes
I'm storing access_tokens for a number of users in my application. When I switch from one account to another for management, I run a background AJAX request on account/verify_credentials to determine if the active user is geo enabled (parameter geo_enabled). If the user isn't geo enabled, I open a lightbox asking them if they'd like to turn on location. I then fire off a redirect to /account/geo if they clicked yes so they can enable location. The problem, at this point, is that the user may be logged into Twitter with a different account. Is there any way for me to do some trickery to switch the logged in user on twitter (i.e. you allow force_login on authentication) to ensure they're logged in as the proper user? Perhaps even some handling to determine the currently logged in user and check if it matches the access_token user? The current handling poses a very big drawback to this beautiful geo page when managing multiple accounts. I need a way of ensuring that / account/geo pertains to the proper user (and not some other managed user account). Any help, solutions, workarounds, or suggestions would be much 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] user:statuses/friends and the following field - feature request
I'm looking for clarification on the call to user:statuses/friends. I noticed that in the returned results there is a following field. It appears as though this field indicates whether or not the screen_name supplied in the request is following the given user. This information, to me, seems quite obvious. We're making a request to retrieve friends after all; it is automatically assumed we're grabbing Mr. screen_name's friends The functionality I would like to see, and I believe would be beneficial meta-data for numerous applications, is that the following field feeds you a boolean value as to whether the user result is following the user associated to screen_name. If I have misinterpreted the field, my apologies. In the API Console, all returned results for my own personal screen_name returned following as TRUE, and I know a number of those individuals off the top of my head are not following me. Could we get this meta-data implemented in the response? I'd be willing to discuss in more detail, I need the information without making additional API calls in order to further improve a weighting/ ranking algorithm I am using.
[twitter-dev] OAuth API Down (or am I just blocked)?
Could a twitter dev let me know if my application has been temporarily blocked? I've got exceptions being thrown on the following in Zend: $this-socket = @stream_socket_client($host . ':' . $port, $errno, $errstr, (int) $this- config['timeout'], $flags, $context); PHP Fatal error: Uncaught exception 'Zend_Http_Client_Adapter_Exception' with message 'Unable to Connect to tcp://api.twitter.com:80. Error #0: php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution' in /.../Zend/ Http/Client/Adapter/Socket.php:235\n If so, could I please talk with somebody about getting this resolved ASAP? My rate limiter was having a problem but I can't even fix the issue until I get access to the API again. Feel free to email me outside of this thread. Regards, Corey
[twitter-dev] Re: Getting feed for multiple accounts (how does hootsuite/tweetdeck do it so fast?)
Make your requests asynchronous so they are handled independently of one another. Each of your 5 API calls for the 5 columns would return their results as soon as they are available for population of the column. On Jul 8, 12:01 am, rksprst alex.kamin...@gmail.com wrote: Let's say I have five columns that show the @replies for five different twitter accounts. Since each account has its own authentication with oath, I would need to make 5 API calls to load up these columns. This seems inefficient and also slow. Is there anyway to speed this process up? Hootsuite seems to do this quite fast, do they actually make a request for every column when you load up their client. Do you guys have any suggestions on improving speed for this? Thanks! Alex
[twitter-dev] Re: OAuth UTF-8 issue
I can also vouch for OAuth UTF-8 issues as I retrieve some funky chars on my side. I went as far as checking the encodings and converting any non utf-8 strings myself to no avail. A very quick example of something that does not work is pulling the name field from the account: http://www.twitter.com/snipeyhead On May 27, 6:43 pm, Alvaro Montoro alvaromont...@gmail.com wrote: Also, if I try to post something like: 私のさえずりを設定する, it works. In fact, if I try to post anything with a japanese character in it, the tweet will go through correctly.
[twitter-dev] Re: users.lookup() pulls by friendship date
Matt, I'm passing individual screen names and/or ids. I understand the full functionality of this API method. My question is more of a feature request because the return data is not particularly useful for what I'm trying to do. Ideally I would want to pass a cursor parameter like many of the other API calls so I can sort over datasets of 100 results. Scenario: I would like to retrieve all specific user's followers screen names (not just 100 of the latest) in the fewest possible API calls. Ideally this would involve checking a next_cursor return variable from the json data. On May 28, 6:27 pm, themattharris thematthar...@twitter.com wrote: Hey cballou, What is the actual API call you are making? I ask because the users/lookup.json method requires you pass it user ids for it to work. If you don't pass it any user ids or screen names you will told that no user matches the specified terms. The data is then returned in an undefined order. As nischalshetty said, this method can be used to request information about any user so the sort order is arbitrary. Are you getting results when you pass no IDs? Matt On May 27, 7:43 pm, nischalshetty nischalshett...@gmail.com wrote: So it's the same one that I was talking about. They haven't specified any sorting rules in the doc, are you sure about it? Before all that, I hope you know that the lookup API can be used to retrieve info about ANY twitter user. So it does not matter if that user is your friend. How will the sorting be applied then? -Nischal On May 27, 5:18 am, cballou ball...@gmail.com wrote: The link is: http://dev.twitter.com/doc/get/users/lookup It actually returns the full dataset for up to 100 users. The returned data is sorted by your newest friendship in descending order. This functionality is quite minimal and could definitely be expanded upon like I suggested above. I was just wondering if there were any possibly hidden parameters I could pass in to change the count, cursor position, etc. On May 26, 1:22 am, nischalshetty nischalshett...@gmail.com wrote: Are you talking about this -http://api.twitter.com/version/users/lookup.format The above API returns whatever ids you have passed. Am I missing something? -Nischal On May 26, 4:38 am, cballou ball...@gmail.com wrote: Nobody? On May 25, 12:14 pm, cballou ball...@gmail.com wrote: I really don't like the fact that calling users.lookup() returns the last 100 users I have friended. Is there a way to retrieve users in a more random fashion or with some kind of ordering (ascending/descending)? I'm looking for more optional parameters. Suppose, for instance, that I have 500 friends. I would not want to pull my last 100 friends when making this API call. I might want to, however, pull a random sampling of 100 of those friends. I may also want to pull a particular number of friends (i.e. imposing a limit on the request). I would propose that there be additional filtering parameters for this request: sort: asc/desc/random (default desc) limit: 1-100 (default 100) Can anybody clarify and expand upon this for me?
[twitter-dev] users.lookup() pulls by friendship date
I really don't like the fact that calling users.lookup() returns the last 100 users I have friended. Is there a way to retrieve users in a more random fashion or with some kind of ordering (ascending/descending)? I'm looking for more optional parameters. Suppose, for instance, that I have 500 friends. I would not want to pull my last 100 friends when making this API call. I might want to, however, pull a random sampling of 100 of those friends. I may also want to pull a particular number of friends (i.e. imposing a limit on the request). I would propose that there be additional filtering parameters for this request: sort: asc/desc/random (default desc) limit: 1-100 (default 100) Can anybody clarify and expand upon this for me?
[twitter-dev] Re: users.lookup() pulls by friendship date
Nobody? On May 25, 12:14 pm, cballou ball...@gmail.com wrote: I really don't like the fact that calling users.lookup() returns the last 100 users I have friended. Is there a way to retrieve users in a more random fashion or with some kind of ordering (ascending/descending)? I'm looking for more optional parameters. Suppose, for instance, that I have 500 friends. I would not want to pull my last 100 friends when making this API call. I might want to, however, pull a random sampling of 100 of those friends. I may also want to pull a particular number of friends (i.e. imposing a limit on the request). I would propose that there be additional filtering parameters for this request: sort: asc/desc/random (default desc) limit: 1-100 (default 100) Can anybody clarify and expand upon this for me?
