Thanks for the update :)
Problem solved here
On Dec 9, 7:32 pm, itcn [EMAIL PROTECTED] wrote:
Alex;
Thanks for the prompt response and updates!! Thanks for all you guys
do,
Barry
On Dec 9, 6:48 pm, Alex Payne [EMAIL PROTECTED] wrote:
Apologies once again. We introduced a regression
I am using the as3 twitter script and am getting the same problems I
think. I cannot get follow to work even though everything is the way
it should be.
do we have an update on this Alex?
On Dec 6, 7:33 am, Alex Payne [EMAIL PROTECTED] wrote:
This is new to me; yours is the only report I've
Hi,
I realized the remaining_hits that the returned value of the
rate_limit_status API was counted down when I tried the other APIs
each time till reset_time.
The design of my application uses this value to know how often I can
use APIs.
# The way to get it is the remain seconds (reset_time -
I realized the remaining_hits that the returned value of the
rate_limit_status API was counted down when I tried the other APIs
each time till reset_time.
The design of my application uses this value to know how often I can
use APIs.
# The way to get it is the remain seconds (reset_time -
I'd need an example of the error you're running into to be sure it's
the same as the one Steve reported. Given the specifics of the
account he's having trouble with, I'm guessing it's not the same
issue.
On Wed, Dec 10, 2008 at 05:49, Ninjamonk [EMAIL PROTECTED] wrote:
I am using the as3
The fix was deployed yesterday, about 17 hours ago. Any incorrect
responses are just cached data that will be evicted over time.
Nothing should live in the cache longer than 24 hours, so all should
be correct within the next 7 hours.
On Wed, Dec 10, 2008 at 08:22, itcn [EMAIL PROTECTED] wrote:
Just wondering if there is any discussion on the current followings
updates not coming through on our ping to the API?
Thanks
I am using the as3 twitter script and so can't get the response just
the 400 bad request. I am thinking its most likely my code if no one
else is getting this.
I wonder if its to do with the flash player I have on my mac.
if its working for others then I wouldn't worry about it.
Cheers
Darren
I'm going to need something more specific than that to help you with this issue.
On Wed, Dec 10, 2008 at 11:23, jje [EMAIL PROTECTED] wrote:
Just wondering if there is any discussion on the current followings
updates not coming through on our ping to the API?
Thanks
--
Alex Payne -
400 usually means that you've run into our rate limit. You can find
out for sure by looking at the body of the response we've sent to you,
which contains an informative error message.
If you need the rate limit lifted for your development period, please
apply for whitelisting at
Hi Jje,
Think you might need to elaborate a bit more.
We might have the same issue (and i have seen it being mentioned in some
other places), but would need more details to ascertain.
Do you get an error, or are the changes in following just not being
reflected?
M
On Wed, Dec 10, 2008 at
Followers are coming through on our call but the Followings and
Updates are not, no error just no #'s. see www.whatsyourtweetworth.com
and enter user name..not all info is coming through and yesterday it
was working.
thanks for the help- developer is out, but he can add more details
once he is
thanks Alex, its not a rate limit issue as I am not hitting it that
much (about 3 times max a minute).
Unfortunately there is not way to get the body of the response in as3
when it throws an error.
Error #2032: Stream Error. URL:
https://twitter.com/friendships/create/shytalk.xml
is an example
Try using a debugging proxy like Charles. It should capture data
coming from your app, whether it's in the browser or an AIR app.
--
Ed Finkler
http://funkatron.com
AIM: funka7ron
ICQ: 3922133
Skype: funka7ron
On Wed, Dec 10, 2008 at 3:27 PM, Ninjamonk [EMAIL PROTECTED] wrote:
thanks Alex,
thanks Ed, spot on. I have it plainly being a POST in as3(well the
twitter script does) but according to charles it was a GET which would
explain the 400.
right off to figure this out.
thanks guys.
On Dec 10, 8:32 pm, Ed Finkler [EMAIL PROTECTED] wrote:
Try using a debugging proxy like
I am currently developing an application to bridge Twitter and
FriendFeed (http://twitter2ff.appspot.com) and I am having a problem
retrieving a complete list of a user's friends.
For example, using the command-line (curl), I retrieved all the
friends for davewiner. His profile
Perhaps it is not returning protected users?
-Original Message-
From: Carter Rabasa [EMAIL PROTECTED]
Date: Wed, 10 Dec 2008 13:27:57
To: Twitter Development Talktwitter-development-talk@googlegroups.com
Subject: Incomplete list of friends being returned
I am currently developing an
I doubt it, because I am authenticating with the user's credentials.
You'd think the authenticated user would get a complete list of their
friends.
On Dec 10, 3:32 pm, Brian Gilham [EMAIL PROTECTED] wrote:
Perhaps it is not returning protected users?
-Original Message-
From: Carter
I've noticed the same sorta' thing. Getting a user's list of followers
and followings has been really flaky. Would love for it to be more
reliable.
Dusty
On Dec 10, 3:46 pm, Carter Rabasa [EMAIL PROTECTED] wrote:
I doubt it, because I am authenticating with the user's credentials.
You'd think
Hi guys, I just started kicking the tires on the API (thanks, btw!)
and am having a horrendous time posting to /direct_messages/new.xml.
The response that comes back is invalid request which doesn't give
me much to debug or go off of. I am able to post to the udpate/status
urls just fine so I
We are seing the exact same thing. Starting late last night, any
attempt made as follows...
https://twitter.com/users/show/{USER}.xml
... Are missing the elements for friends and status updates. Not
showing a zero. The elements are just missing from the response.
Twhirl is showing zeros
If you provide the full request/response output from your call to the
method, I'm sure somewhat can tell you what's going on. Thanks!
On Wed, Dec 10, 2008 at 16:36, sMan [EMAIL PROTECTED] wrote:
Hi guys, I just started kicking the tires on the API (thanks, btw!)
and am having a horrendous
We are seing the exact same thing. Starting late last night, any
attempt made as follows...
https://twitter.com/users/show/{USER}.xml
... Are missing the elements for friends and status updates. Not
showing a zero. The elements are just missing from the response.
Twhirl is showing
Alex,
I think there might still be an issue with this fix. I've run through
many test cases (including your profile) and all of them are still
failing to return the full user object.
It looks like this might be just an issue with the xml format of /
users/show (the json output seems to contain
I have had the same issue since some time last night.
Basically, the following and update elements of the output just
don't come through
I believe this was resolved last night, but most of my users are still
having the problem (and I'm getting increasingly worried that it's not
just an issue
Just tested myself.
https://twitter.com/users/show/damon.xml
user
...
nameDamon Clinkscales/name
screen_namedamon/screen_name
...
followers_count676/followers_count
status
...my most recent status is here...
/status
/user
No friends_count (or following_count), though.
-damon
Just tested myself.
https://twitter.com/users/show/damon.xml
user
...
nameDamon Clinkscales/name
screen_namedamon/screen_name
...
followers_count676/followers_count
status
...my most recent status is here...
/status
/user
No friends_count (or following_count),
Still the same problem; the XML version of the API no longer seems to
be returning the full data. It never made sense that this would be a
cache issue; beacuse this should return new data every time we request
the XML file; what good is data that is 24 hours old?
On Dec 10, 12:23 pm, Alex
Looking into this one further...
On Wed, Dec 10, 2008 at 17:21, itcn [EMAIL PROTECTED] wrote:
Still the same problem; the XML version of the API no longer seems to
be returning the full data. It never made sense that this would be a
cache issue; beacuse this should return new data every
The friends method
Returns up to 100 of the authenticating user's friends who have most
recently updated, each with current status inline. It's also possible
to request another user's recent friends list via the id parameter
below.
but this method does not provide an easy way to get all my
You can page through that method to get all of your friends.
On Wed, Dec 10, 2008 at 18:02, Lien Tran [EMAIL PROTECTED] wrote:
The friends method
Returns up to 100 of the authenticating user's friends who have most
recently updated, each with current status inline. It's also possible
to
Just a reminder: today was the day for this change to go live, and it
just went live.
On Thu, Dec 4, 2008 at 12:42, Brooks Bennett [EMAIL PROTECTED] wrote:
I agree, this is a great change.
On Dec 3, 11:07 pm, dean.j.robinson [EMAIL PROTECTED]
wrote:
return the representation of the
When you no longer get any User objects in the response.
On Wed, Dec 10, 2008 at 18:08, Lien Tran [EMAIL PROTECTED] wrote:
The problem is that I hit the rate limit error very easily when I do
this. How do I know when I got all my friends and when to stop
paging?
On Dec 10, 6:06 pm, Alex
Thanks Alex, looks great.
I'm playing with it now and am looking to use it to replace the
additional show/user.json call that I previously needed. There are a
few properties that are in user/show but not in the verify_credentials
method, I was wondering if there are plans to include these in a
It does return an error (along with the header) as well. Thanks for
adding the user data to this call. Saves an extra call for our
service.
--
Swap
On Dec 11, 7:07 am, Alex Payne [EMAIL PROTECTED] wrote:
Just a reminder: today was the day for this change to go live, and it
just went live.
yeah, it is very easy to page through... the only thing that worried
me was when doing a delete operation and not really knowing for sure
if the number of friends was correct. i don't think the api returns
'how many friends' (but maybe my memory is faulty) - the thing i was
worried about is if
that would be brilliant, it would allow me to completely eliminate the
additional api call I'm using, while making sure I can still keep
users profile settings up to date on each login.
no rush though, thanks in advance :)
On Dec 11, 2:34 pm, Alex Payne [EMAIL PROTECTED] wrote:
I can have it
I am no longer seeing created_at in the returned user record for
http://twitter.com/users/show/id.xml.
Naturally, this has broken Follow Cost. :(
Thanks,
--
Barry
http://followcost.com
On Dec 10, 7:39 pm, Alex Payne [EMAIL PROTECTED] wrote:
Looking into this one further...
On Wed, Dec
38 matches
Mail list logo
