RE: Why Only 1 Block?
You are viewing a single comment's thread:
I remember Steemit broke my python steem library asyncsteem back in the day, by creating clueless rate-limiting like this. Sad to see hive-engine is basically repeating history in that sense.
I used to run a script once a week back on STEEM that streamed one day worth of blocks and from that input created a daily report of the flag-wars that were at their peak back then. The SteemitInc introduced their brean-dead rate-limit, and my reports were instantly dead.
There is a draft RFC describing three HTTP headers for (one form of) proper rate limiting. There are other (incompatible) header sets for rate limiting used by existing services, but right now for anyone implementing rate limiting on web APIs, there really is little to no excuse not to use these headers as described in this draft
Having to set some hard coded delay to stream blocks because the server implements brain-dead rate-limits is silly beyond words.
That's one thing, but at least hive (and steem) has get_blocks, where you can query for a range of blocks in a single call.