So it only works with POST for me when using authentication. Not sure
if this is an issue with the API itself.
On Aug 9, 12:17 pm, Justin justin.cooper...@gmail.com wrote:
I'm using the users/lookup.json API and passing a valid list of
user_ids that I retrieve from friends/ids (yes, there are
Hi Adrian,
Glad that you've noticed. We have indeed fixed this bug and thanks for your
patience while we tackled it -- a bit more complex than it appeared on the
surface. If you do continue seeing any issues in this area, please report
them to us so we can take a look.
Thanks,
Taylor
@episod
I still have at least 47 Twitter IDs that are affected. For example:
http://api.twitter.com/1/users/show.xml?user_id=71691990
XML preamble, no XML document. JSON method returns zero-byte response.
On 5/4/11 3:54 PM, Taylor Singletary wrote:
Hi Adrian,
Glad that you've noticed. We have
Dossy,
Thanks -- this appears like it may be a different issue, but I'll need more
user_ids to be sure. Can you follow up with me off-list and send me the
array of user_ids that you're seeing this behavior for? epi...@twitter.com
Thanks,
Taylor
@episod http://twitter.com/episod - Taylor
Glad to hear you got it working Gabe. I'm not sure what was causing it to
not work but the full URL is not required and the following shortened
version should work fine. I also noticed you had a space before the second
screen_name that you probably shouldn't include.
$userDeets =
Neither works. Am I processing the results correctly?
On Apr 12, 3:25 pm, Abraham Williams 4bra...@gmail.com wrote:
Try:
$userDeets = $connection-get('users/lookup' array('screen_name' =
'biz,twitterapi'));
That should work.
Abraham
-
Abraham Williams | Hacker Advocate |
Thanks to Abraham for reminding me about var_dump which showed the
results as NULL.
At risk of outing myself as stupid I will do so anyway in case there
might be someone out there who has also been searching for how to do
this, from start to finish.
This code works. The stupid part was not
Bit more on this one, I am using include_entities set to true and
getting the junk results. If I turn it off I get the correct results
but I need the entities.
Cheers
On Apr 9, 3:34 pm, Ninjamonk dar...@stuartmedia.co.uk wrote:
Before I post this as an issue is anyone else getting this problem.
Thanks for investigating :) Just thought I'd add that I'm also affected by
this, and when I investigated I discovered that the exact selection of users
which are omitted and duplicated is relatively stable; that is, if I run the
same set of lookups on the same chunks of 100 users, it will
hi all.
we're actively investigating this issue.
On Fri, Mar 11, 2011 at 8:13 PM, gcoats84 gary.co...@gmail.com wrote:
I am also running into these issues with users/lookup.json. The ids I
have issues with are totally random.
Sometimes the duplicates are back to back, other times they are
I am also running into these issues with users/lookup.json. The ids I
have issues with are totally random.
Sometimes the duplicates are back to back, other times they are
separated by a few records.
example screen names that are all returned duplicates:
yaneeduh, JDH1127, MelxWeasley, ealderson,
Hi,
I too am getting duplicate results and some of the valid ids are not
beings returned. If it helps, these ids would replicate all the issues
faced :
11825, 248874232, 28296091, 251642658, 257793455, 225992183,
85168850, 92509004, 113697273, 99673641, 99253238, 98032551, 91619850,
I have noticed this strange behaviour too (duplicated results and
unknown users). For instance, yesterday, when I tried to lookup for
user 44537294 (with two different accounts), I received during many
hours information about user 243784138, before receiving expected
result (around 17/18h UTC).
It looks like things are working again. Thanks unknown developer. I
also noticed that the extensions (json,xml,atom) seem to be case-
sensitive. I don't know how I got this far without noticing that.
On Jun 3, 9:04 pm, Mo maur...@moluv.com wrote:
I might be overlooking something, but it seems
Hello Abraham,
You're right. I did not check the response of home_timeline well
enough, I'm sorry for missing that.
However, I'm still having some troubles, let me try to do a better job
on explaining them.
1. The main problem is using users/lookup in a test application in
which I provide
Hello Matt,
Thanks for trying again (I did only see your answer just now, sorry).
Good to know you've found out that the console is not seeing the
parameters. Thank you very much for filing it in the issue tracker.
This means that I only have one question left: can someone tell me if
users/lookup
After some research in my own application it appears that I forgot to
UrlEncode the parameters of the users/lookup query. By incident I
hadn't used any special characters in the parameters until now, so I
didn't notice this earlier.
Conclusion:
- Matt addressed the issue that the console on
Hey Abacadabrados,
You need to give the user lookup request some valid user ids or screen
names. The error you are receiving is because you are sending a
user_id of 0 which is not a valid account. Maybe try with your screen
name first.
You can find more information on how the method works on
Hello Matt,
Thank you for your quick and clear response.
However, the user id and screen name are both valid. Both User_id = 0
or screen_name = twitterapi work perfectly in the API Console for home/
timeline - but not for users/lookup. I also tried it with my
screen_name, this works fine with
home_timeline always shows the statuses for the authenticated user not the
user_id you pass in a parameter.
As you can see there is no user with the id of 0: http://goo.gl/DpWe
Abraham
On Sat, May 29, 2010 at 22:33, Abacadabrados rene.rikk...@gmail.com wrote:
Hello Matt,
Thank you for your
Sorry EPI twitter is confusing, I meant the Twitter-Async library. The
issue is oAuth and sending the comma list.
Has anyone got users/lookup with multi usernames working with oAuth?
On Apr 22, 10:22 pm, Ninjamonk dar...@stuartmedia.co.uk wrote:
thanks, works in the browser now, however the
thanks, works in the browser now, however the corrected oAuth call
does not work and gives me a 401. Is there trick to getting this
method to work with oAuth? I noticed someone else was having problems
with it.
As I said before every other api method call works except this one.
for example this
22 matches
Mail list logo
