On Sep 4, 4:43 pm, Andrew Badera and...@badera.us wrote:
ATOM _is_ XML ... not sure what the problem is?
Uh, yes ... at a basic level that's true -- but the fact that you
would point that out suggests that you aren't remotely familiar with
the various response formats twitter API calls. Let
Hi Jesse,
Just like to chirp in and say I'm seeing weirdness too. Particularly, /
followers/ids is taking more than 10 seconds to return for all
accounts with over 30k followers, or alternatively are failing with
401s (using OAuth tokens). Since 10s is the hard limit for AppEngine,
my app cannot
So that is why my cron jobs are suddenly taking forever to complete,
since Saturday morning.
This 10 second delay is a new bug. In the past one just got a lot of
502 errors when retrieving really large accounts, but even those calls
were seldom longer than 1 second.
Dewald
On Sep 6, 5:00 am,
Also, go here: http://twitter.com/account/connections and see if there
are any applications that you've authenticated to via OAuth that might
be doing it. (That's the other way this can happen.)
On Sep 5, 3:14 pm, Dewald Pretorius dpr...@gmail.com wrote:
Change your Twitter password
I can't speak to the policy issues, but I'll share a few things about
social graph backing stores.
To put it politely, the social graph grows quickly. Projecting the
growth out just 3 or 6 months causes most engineers to do a spit-
take.
We have three online (user-visible) ways of storing the
Hi Ryan,
I am getting the same error - i can found it in the logs of my app
every day - at least 20 times.
1. The IP of the machine making requests to the Twitter API. If you're
behind NAT, please be sure to send us your *external* IP.
---
Name:twittme.mobi
Address: 67.222.129.154
2. The
Hello Abraham,
currently this method is returning empty response e.g. .
If it returns empty response - my application knows that this is
sicessfull login,
otherwise - it prints the error.The docs regarding this should be
updated.
Greetings!
On Sep 5, 12:27 pm, Abraham Williams
Hey Jesse,
I've seen random failures and timeouts in the past, but in the last 48
hours they have become very consistent. I've got 4 accounts that have
just 'stuck'. Very tempted to just close up the app.
David
On Sep 6, 9:13 am, Jesse Stay jesses...@gmail.com wrote:
David, that's a
Random 408 errors are being returned when users are attempting to
Sign in with Twitter on my site TweetMeNews.com.
Has anyone else been seeing this? Twitter, is there any way you can
expand on the error message instead of just saying 408? That would
help us better Understand Report what's
Thanks John. I appreciate the various ways of accessing this data, but when
you guys make updates to any of these, can you either do it in a beta
environment we can test in first, or earlier in the week? Where there are
very few Twitter engineers monitoring these lists during the weekends, and
Hi devs,
I just got an android phone. Can anyone make a recommendation for a
good twitter android app? It seems there are few. Anyone specifically
working on one and need a tester?
~Blaine
Yeah it's happening to me again, same as my previous email, except the
time stamp will be around 2 minutes ago
On Sep 6, 4:05 pm, twittme_mobi nlupa...@googlemail.com wrote:
Hi Ryan,
I am getting the same error - i can found it in the logs of my app
every day - at least 20 times.
1. The IP
I have seen this same http page with empty body
!DOCTYPE html PUBLIC -//W3C//DTD HTML 4.01//EN http://www.w3.org/
TR/1999/REC-html401-19991224/strict.dtd
!-- !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01//EN
http://www.w3.org/TR/html4/strict.dtd; --
HTML
HEAD
META HTTP-EQUIV=Refresh CONTENT=0.1
META
For now, we're sending the row-count-queries queries back to the
second system, which is otherwise idle, but isn't consistent with the
first or third system.
Can you help us better understand what queries you're talking about?
Do you mean, e.g., that any queries that call for *ALL* friends/ids
On Sun, Sep 6, 2009 at 11:18 AM, Jesse Stay jesses...@gmail.com wrote:
Thanks John. I appreciate the various ways of accessing this data, but
when you guys make updates to any of these, can you either do it in a beta
environment we can test in first, or earlier in the week? Where there are
I don't understand how asking to release features earlier in the week is
asking a lot? What does that have to do with scaling social graphs?
Jesse
On Sun, Sep 6, 2009 at 2:49 PM, Nick Arnett nick.arn...@gmail.com wrote:
On Sun, Sep 6, 2009 at 11:18 AM, Jesse Stay jesses...@gmail.com wrote:
On Sun, Sep 6, 2009 at 1:52 PM, Jesse Stay jesses...@gmail.com wrote:
I don't understand how asking to release features earlier in the week is
asking a lot? What does that have to do with scaling social graphs?
I was referring to a beta environment.
Nick
Has anyone heard of any Skype Apps that tie into the Twitter API, or vice
versa. Look for some examples of how one might integrate the two.
I can't find anything live. I realize it might be minimal since we're
talking about one web based, and one client based, but thought I would ask.
--
Dale
I meant to type, LIMIT 100, 5000.
John,
Thanks for the background info. Row count queries means to me the
summary friends and followers numbers displayed on the Twitter web
pages, and returned on the user profile via the API, correct? So, if I
am understanding you correctly, then the friends and followers that
we're getting back
There is no way that paging through a large and volatile data set can
ever return results that are 100% accurate.
Let's say one wants to page through @aplusk's followers list. That's
going to take between 3 and 5 minutes just to collect the follower ids
with page (or the new cursors).
It is
We are seeing this HTML META REFRESH as well from our clients. We are
a mobile application and seeing this issue more and more frequently to
the point that application is not functioning properly, its hard for
use to provide any specific ip data as the carriers are most likely
proxying the
Agreed. Is there a chance Twitter can return the full results in compressed
(gzip or similar) format to reduce load, leaving the burden of decompressing
on our end and reducing bandwidth? I'm sure there are other areas this
could apply as well. I think you'll find compressing the full social
If I worked for Twitter, here's what I would have done.
I would have grabbed the follower id list of the large accounts (those
that usually kicked back 502s) and written them to flat files once
every 5 or so minutes.
When an API request comes in for that list, I'd just grab it from the
flat
The other solution would be to send it to us in batch results, attaching a
timestamp to the request telling us this is what the user's social graph
looked like at x time. I personally would start with the compressed format
though, as that makes it all possible to retrieve in a single request.
On
As far as retrieving the large graphs from a DB, flat files are one way -
another is to just store the full graph (of ids) in a single column in the
database and parse on retrieval. This is what FriendFeed is doing
currently, so they've said. Dewald and I are both talking about this
because
26 matches
Mail list logo
