You are viewing a single comment's thread from:
RE: Proposals: STEEM citizenship comes with both rights and responsibilities
Maybe remlaps recent post could help you
https://steemit.moecki.online/hive-151113/@remlaps/getting-steem-python-to-run
Maybe remlaps recent post could help you
https://steemit.moecki.online/hive-151113/@remlaps/getting-steem-python-to-run
Thank you, that definitely looks promising, I'll give it a try, although meanwhile I was having fun with json-ing the APIs directly. :)
@the-gorilla, I couldn't find in Condenser a method that returns a list of the active API full nodes?
Beem has NodeList().get_steem_nodes() and I have no idea where that info comes from...
Code:
from beem import Steem
from beem.nodelist import NodeList
nodelist = NodeList()
nodelist.update_nodes()
nodes = nodelist.get_steem_nodes()
print(nodes)
Output:
['https://api.justyy.com', 'https://cn.steems.top', 'https://api.steemit.com', 'https://api.steem.buzz', 'https://api.steem.buzz', 'https://steem.61bts.com']
The NodeList class has some standard nodes and updates itself depending on availability. There is an account @fullnodeupdate for this purpose. The results of the check are stored there for everyone to access. Unfortunately, the node list is no longer maintained by beem (on Steem?). The last account update was in November 2022, so the current new nodes (e.g. mine) are not even included there.
If you would like to know which current nodes are available with which response times, you can use these pages:
https://steemyy.com/node-status.php
https://ecosynthesizer.com/steem/nodes
You can add the best nodes for you to the Steem object as a list.
Thank you! When I was searching online for the most up-to-date list of the full nodes, I found a few resources that are different from those you shared :)))
Justyy's page says these response times are from the browser but that didn't made any sense to me, as logically that would be the response times from where that page is hosted, so I pinged some of the nodes from my command prompt and got completely different response times.
That whole matter came to me as I am a sucker for efficiency and I'd like to use the fastest node that's as close as possible to me :)))
The most logical thing would be the full-nodes list to be available through a Condenser method but it seems that isn't available, one of the downsides of decentralization, I suppose :)
Not necessarily. For example, if the queries are executed on the client side. This is also the case on Justyy's page. I can also confirm this, because in my case the scripts are blocked by default and I can see on Justyy's site that the information is only available when I allow the requests to the respective servers. The speed is therefore only measured in the browser.
I can't tell you how the times are measured. However, if you measure the speed with Ping, the data will of course differ.
I think you're right and it seems to me those response times on the page are bigger because they include the api method processing time as well ;) Ping will always be faster unless it's a method that does nothing :)