Without prior notice, I can understand (circumstances), but without
any kind of subsequent announcement?? Means we have to discover issues
ourselves, verify that they're Twitter related (and not internal),
then search around for existing discussion on the topic. Saves us a
lot of time and
there may be a
way to get an account white-listed for the good results to this
method!
At very least, can you let us know when we can expect extended periods
of consistent, correct behavior from related_tweets, so I can
(re)set expectations w/ my clientele?
Thanks,
- Waldron Faulkner
Our app had same issue, was mostly OK overnight, but we did see the
odd failure.
Is there an update on what happened? Thanks!
- Waldron
GraphEdge.com
On Nov 11, 1:29 pm, Yu-Shan Fung ambivale...@gmail.com wrote:
Hi All,
I've been getting a high number of 500 errors (about 50% of the time
I'm completely on board with any strategy that will simplify (or
especially amplify) the amount of graph data I can get. I had a
discussion recently with Ryan where he indicated an openness to ideas
of this sort because there is (he says) no getting around the 20K rate
limits... an idea I find
Are you sure your requests are coming from the same IP you
whitelisted? If you're on a shared host, for example, your outbound
requests may come from a different IP as your dedicated inbound IP. I
had this issue, had to bind curl to my dedicated IP, and it worked
fine. Setting the
Hey, Twitter API staff, can you recommend a next step for me to take?
It's been more than a week since I issued a rate-limit request, and I
haven't heard anything, nor seen any changes. What to do when the rate
limit request form yields radio silence? Thanks!
- Waldron Faulkner
@WaldronFaulkner
The rev-share doesn't kill the deal for me, although it does feel
steep, and just because Apple gets 30% for the app store, not sure
that number works in all cases. Also 60 day terms are discouraging.
But the killer for me is the support-only clause. If I can't own the
relationship, that makes it
For the record, it's not because I have an account that's suspended,
it's because I want to know whether my analytics platform I can
permanently stop tracking suspended accounts, or whether I have to
periodically check back in to see if they're still suspended. I wonder
what the rate of
I can save a lot of trouble if I know that a previously suspended
Twitter user won't later have his/her suspension lifted.
Anyone??
Waldron
Thanks API team for implementing the cursoring, really needed it
(could you tell!?). I have to go implement that right now.
On Sep 16, 9:24 am, citricsquid s...@samryan.co.uk wrote:
This.
I've always thought that the obvious path would be to have unique
error codes that never change. So if
don't have to go do a Facebook app instead. Please
tell me that someone was working on this over the weekend.
I'd love to have some solid, no-nonsense response to this, with hard
dates. So far we've had well-meaning but empty words.
Thanks,
- Waldron Faulkner
Founder, GraphEdge LLC.
http
Hello, Raffi,
This is not the non-json response issue. This is open, accepted, high
priority issue #1019. Be the hero that fixes this for us, it's
breaking my back. Ryan and Alex aren't helping me out, maybe you can
be THE MAN! Please fix this, PLEASE!
On Sep 14, 6:36 pm, Raffi Krikorian
to developers on a best-effort basis. For the vast majority of Twitter
applications, this data isn't necessary. A specialized class of
applications need this data, and we're doing our best to provide it.
On Tue, Sep 15, 2009 at 00:21, Waldron Faulkner
waldronfaulk...@gmail.com wrote:
Ryan
, Sep 13, 2009 at 8:55 AM, Waldron Faulkner
waldronfaulk...@gmail.com wrote:
PLEASE, can someone on the API team let us know when the paging bug(s)
with followers/ids (and friends/ids) will be addressed? There have
been problems with it for weeks, but now it's just downright broken.
We
PLEASE, can someone on the API team let us know when the paging bug(s)
with followers/ids (and friends/ids) will be addressed? There have
been problems with it for weeks, but now it's just downright broken.
We can't get lists of followers for users with large numbers of
followers. That's a basic,
Hey developers, any hints/tips on how I can get the Twitter API team
to focus on this issue? It's hard to build a business on the Twitter
API when a crucial feature like this just stops working and we get
radio silence for days. Any tips on how I can help the team focus on
this??
On Sep 9, 10:10
I could really go for jittery right now... instead I'm getting
totally broken!
I'm getting two pages of results, using ?page=x, then empty. To me, it
looks like all my accounts have max 10K followers. I'd love some kind
of official response from Twitter on the status of paging (John?).
Example:
Same oddness w. friends count as well? I'd guess so.
My problem is that if I try to get followers using paging, I get
different numbers (and different followers) than if I pull the entire
list w/o paging. Also, followers disappear and reappear from one hour
to the next.
On Sep 2, 5:44 pm, Jason
Strange events w/ Rate Limit requests.
I'm calling the API from my whitelisted IP and getting results that
are all over the map. It's almost as if Twitter is load-balancing my
requests to two different environments, each of which is keeping its
own count of my rate limits. So my app chugs along
The explanation I've had makes sense. If you call from a whitelisted
IP, it charges to the IP limit, regardless of authentication. IE, it,
checks that first.
On Aug 12, 5:30 pm, Zaudio si...@z-audio.co.uk wrote:
I get the same with my apps; an authenticated and unauthenticated call
to get rate
Getting same response to my rate limit requests (http://twitter.com/
account/rate_limit_status.format), for both Account and IP.
I think I missed something. I used to have two different, independent
numbers for my account and IP rate limits (including different reset
times). That is, I would
21 matches
Mail list logo
