HttpServer returns time estimation to targetblock. As image.
- Rendered at request, variable heading, fontsizes, fontfaces, colors.
- Any NXT or HZ targetblockheight. Other coins soon. Future dreams.
-
Quote of the day: " If you can break it, you have grokked it. " (AltSheetsDev 2015/08/10)
-
@news
-
-
v14: Much wow tools - Several node servers! Peerexplorer DNS crawler. HZ peer crawler!
- "126 nodes, 57 with openAPI, 37 have DNS names."
-
v13.5: measurements NXT & HZ blocktimes; v14.2 = NXT faster blockspeed (numbers, code), measured HZ and BURST too
-
v13: Docker magic & autostarting using systemd
-
v12: my very first Dockerfile and Hub repo altsheets/chaincountdown
-
v11: "Conceptual Thunderstorm"
-
v10: font & static pages improvements
-
v09 linux server install readme
-
v08 much: new option font; refactoring: massive reorg of the code, cleaned up
v14: Much wow tools:
- "126 nodes, 57 with open API, 37 of which have domain names"
- Several node servers! Peerexplorer DNS crawler. HZ peer crawler!
-
-
-
Why? A user complained to me that my image server is broken ...
-
... but jxnt.org was down, which I had been using for API queries (of 'getBlockchainStatus' --> blockNumber).
-
New solution: Whenever an API lookup is failing, the next server is asked. Only if all are failing, my server is in trouble.
-
Now server names are hardcoded in config, so I wanted servers which may last a while. Choosing by looking at their domain names.
-
Using the peerexplorer.com openApi list, I looked up all domain names, and sorted them fancily (backwards, by TLD first!)
-
Then, when it came to HZ, I was lacking peerexplorer - so I created my own Horizon Peer Crawler (#HPC): 57 nodes with open API
-
I could recycle the above DNS lookup: 37 of which have domain names.
-
And in the end, I even added a test if an IP is answering on port 7774 - so now I know: 126 nodes.
I started this session (the 3rd after waking up 26 hours ago) in a MINDMAP software.
-
-
-
-
-
What inspired me much ... to still continue, and happily... was this reaction :
- " It works! This is awesome. Tomorrow, i will make it work for ethereum. "
- Thanks! Feedback is a booster ...
-
The python code for this server is also for sale. Contact me for details. Or not. Spend your money for other things. But spend it - keeping money creates a foul odor.
v14: Much wow tools:
+ "126 nodes, 57 with open API, 37 of which have domain names"
+ Several node servers! Peerexplorer DNS crawler. HZ peer crawler!
+
+
+
Why? A user complained to me that my image server is broken ...
+
... but jxnt.org was down, which I had been using for API queries (of 'getBlockchainStatus' --> blockNumber).
+
New solution: Whenever an API lookup is failing, the next server is asked. Only if all are failing, my server is in trouble.
+
Now server names are hardcoded in config, so I wanted servers which may last a while. Choosing by looking at their domain names.
+
Using the peerexplorer.com openApi list, I looked up all domain names, and sorted them fancily (backwards, by TLD first!)
+
Then, when it came to HZ, I was lacking peerexplorer - so I created my own Horizon Peer Crawler (#HPC): 57 nodes with open API
+
I could recycle the above DNS lookup: 37 of which have domain names.
+
And in the end, I even added a test if an IP is answering on port 7774 - so now I know: 126 nodes.
I started this session (the 3rd after waking up 26 hours ago) in a MINDMAP software.
+
+
+
+
+
What inspired me much ... to still continue, and happily... was this reaction :
+ " It works! This is awesome. Tomorrow, i will make it work for ethereum. "
+ Thanks! Feedback is a booster ...
+
The python code for this server is also for sale. Contact me for details. Or not. Spend your money for other things. But spend it - keeping money creates a foul odor.