5

This is really annoying. I was testing a script that pulls pages from the API according to the published throttle guidelines. Then I went to StackApps to do something - and lo and behold, this is what greets me:

We're sorry...


There are an unusual number of requests coming from this IP address.
To protect our users, we can't process any more requests from this IP address right now.
We'll restore access as quickly as possible, so try again soon.
If you believe you have reached this page in error, contact us.

Since when did using an API app affect the site itself??? This is surely a bug.

Note: I'd have posted this on StackApps, but can't for obvious reasons.

Update: I've been able to reproduce this behavior, so it's not a random quirk.

Steps to reproduce:

Improve this question
8
  • @thyrgle: But I can still access Meta, so....
    – uɐɯsO uɐɥʇɐN
    Sep 4 '10 at 21:49
  • @George A loophole! Excellent...
    – Michael Mrozek
    Sep 4 '10 at 22:28
  • @Michael: A loophole...? In what...?
    – uɐɯsO uɐɥʇɐN
    Sep 4 '10 at 22:39
  • @Michael: Oh. Well this is a serious bug report.
    – uɐɯsO uɐɥʇɐN
    Sep 4 '10 at 22:57
  • @Micheal Mrozek: Now there's the real problem...
    – thyrgle
    Sep 4 '10 at 23:24
  • 3
    ++ but I think the salient issue here is that the API throttle is not performing to spec, despite any insistence that it is. see stackapps.com/questions/1457/…
    – Sky Sanders
    Sep 5 '10 at 1:25
  • 1
    @code: Whatever it is... it's a bug and the status-bydesign tag should be removed.
    – uɐɯsO uɐɥʇɐN
    Sep 5 '10 at 2:00
  • 1
    I suggest this whole discussion is moved to the StackApps site. It's pointless and noise on meta and there is a site dedicated to it. If you can't post on StackApps, then contact the devs via email
    – BinaryMisfit
    Sep 5 '10 at 13:46
3

So, what you're saying is that you violate the terms of use of the API and are then surprised when you get a temporary ban from the network?

If you get a ban from the sites, you'll also be banned from the API too you know.

Improve this answer
13
  • 1
    Have fun outside George! The graphics are really nice there...
    – thyrgle
    Sep 5 '10 at 0:37
  • @thyrgle - do note that the ban is currently something like 2 minutes, its not a permanent thing. Might be long enough to get your shoes on.
    – Kevin Montrose
    Sep 5 '10 at 0:42
  • 4
    @Kevin: You didn't read my question - it says "a script that pulls pages from the API according to the published throttle guidelines ". It was not violating anything.
    – uɐɯsO uɐɥʇɐN
    Sep 5 '10 at 1:15
  • @George - no, you're running code that claims it doesn't.
    – Kevin Montrose
    Sep 5 '10 at 1:41
  • 2
    @Kevin: Where is this claim?
    – uɐɯsO uɐɥʇɐN
    Sep 5 '10 at 2:00
  • @George - claims it doesn't "violate the published guidelines," sorry for the ambiguity. We've tested this many times and never repro'd with any code that's not Soapi. All evidence suggests its not a problem on our end, and its ill advised to run at "throttle limits" anyway. We're not going to waste manpower investigating this, yet again.
    – Kevin Montrose
    Sep 5 '10 at 2:23
  • 3
    I don't make any 'claims' that are not backed up by hard numbers that are completely transparent. A spec is a spec. If running at spec is 'ill advised' then the problem is not with the code, it is with the spec or the implementation thereof. In any case, 30 request per 7 seconds is not at throttle limits of 30 requests per 5 seconds.
    – Sky Sanders
    Sep 5 '10 at 2:36
  • 2
    For those who are interested the tests that 'claim' to run at and well under spec yet fail are located here: soapi.info/Code/JS2/latest/Tests/ThrottleTests.htm and the post upon which you are welcomed to post feedback regarding results or the veracity of the tests is here stackapps.com/questions/1457/…
    – Sky Sanders
    Sep 5 '10 at 3:09
  • 2
    @Kevin: Well, I've spent time writing an app that doesn't work - something needs to get fixed.
    – uɐɯsO uɐɥʇɐN
    Sep 5 '10 at 3:37
  • @George - ... you've written a client side [app] that makes 30 reqs a second? What happens when the user runs another [app]?
    – Kevin Montrose
    Sep 5 '10 at 4:05
  • @Kevin: I don't know. If it helps at all, you can find it here: stackcenter.quickmediasolutions.com/display2.php
    – uɐɯsO uɐɥʇɐN
    Sep 5 '10 at 4:18
  • 3
    @George - ... no, I mean if your [app] is client side and is making 30 requests a second it will break the instant the user has another [app] installed. Frankly, its misunderstandings like this that make me want to rescind the throttle documentation and phrase it like "The # of requests X users would reasonably make in Y seconds". This obsession with making the maximum number of requests possible is completely missing the point.
    – Kevin Montrose
    Sep 5 '10 at 4:52
  • 2
    george's app uses the default soapi.js2 throttle settings of max 30 requests per 7 seconds with no more than 10 concurrent active requests and it seems to work just fine. no one is obsessed with squeezing the most requests and this has been made clear. you published a spec and everyone is making efforts to respect it. The issue of multiple apps is a straw man in this conversation, in another it would be story that supports server side throttling.
    – Sky Sanders
    Sep 5 '10 at 8:05

Not the answer you're looking for? Browse other questions tagged .