Working on the txjsonrpcqueueu library, I created this script as a precursor to a DNS based injector system I am working on.
The script itterates over a number of API calls using the txjsonrpcqueue library for each of the full API nodes below.
It currently appears there are ZERO fully working full API nodes available.
The api.steemit.com nodes and the api.steem.house seem to be almost full API, yet they seem to lack support for the tags API based calls. Other commonly disabled API's seem to be the reputation and the tags API.
| Node | rc | reputation | tags | everything else |
|---|---|---|---|---|
| steemd.privex.io | FAIL | OK | OK | OK |
| appbasetest.timcliff.com | FAIL | PARTIAL | OK | OK |
| gtg.steem.house:8090 | FAIL | FAIL | FAIL | FAIL |
| anyx.io | FAIL | FAIL | FAIL | FAIL |
| api.steemit.com | OK | OK | FAIL | OK |
| api.steemitstage.com | FAIL | FAIL | FAIL | FAIL |
| api.steem.house | OK | OK | FAIL | OK |
| api.steemitdev.com | FAIL | FAIL | FAIL | FAIL |
| steemd.minnowsupportproject.org | OK | PARTIAL | OK | OK |
| rpc.usesteem.com | OK | PARTIAL | OK | OK |
| rpc.steemviz.com | OK | PARTIAL | OK | OK |
| rpc.curiesteem.com | FAIL | FAIL | FAIL | FAIL |
| rpc.steemliberator.com | FAIL | FAIL | FAIL | FAIL |
I will look at improving the script with specific errors produced by the nodes (some of the across the board failing nodes don't actually give back a proper JSON-RPC error responses in a batch context).
The 400 response from https://anyx.io seems particularly peculiar. It indicates a problem with the request as sent by the client, but this is exactly the same request all other nodes are sent.
At the moment, it seems I am going to have to rethink the DNS injector concept.
