As the high CPU usage of our account history nodes, we have added some new limit rules.
All visits to https://api.steemit.com will be affected by these rules.
Rules
1.All API requests are limited by 100requests/second.
2.These five API methos below have been limited in 10 requests per second per IP .
- condenser_api.get_account_history
- account_history_api.get_account_history
- condenser_api.get_ops_in_block
- condenser_api.get_discussions_by_feed
- condenser_api.get_discussions_by_author_before_date
3.These two API methos below have changed their upper limit from 10000 to 20 each time.
- condenser_api.get_account_history
- account_history_api.get_account_history
Notice
This is not the final setting.
!thumbup
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Hello @ety001! You are First-rate!
command: !thumbup is powered by witness @justyy and his contributions are: SteemYY.com
More Commands are coming!
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
!ask What is a normal rate limit rule to an API?
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
A normal rate limit rule to an API would be to limit the number of requests that can be made within a certain amount of time. For example, a rate limit rule may allow a maximum of 1000 requests per minute or 100 requests per second.
command: !ask is powered by witness @justyy and his contributions are: SteemYY.com
More Commands are coming!. !ask is currently based on ChatGPT-3.5
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Thank you for sharing the the updated rules.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
I hope this update will make STEEM more resilient. Thank you for your effort!
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit