This post is intended to cover the server costs for SteemWorld.org and to enable me to continue my development in the future.
In case you missed the first part:
SteemWorld ~ Weekly Support ~ #1
Dieser Post ist dafür gedacht die Serverkosten für SteemWorld.org zu decken und mir in Zukunft weitere Entwicklungen zu ermöglichen.
Falls du den ersten Teil verpasst haben solltest:
SteemWorld ~ Weekly Support ~ #1
We are now running on the new server and it looks like all features are working properly. If you didn't have any issues using SteemWorld in the past week, that's a good thing and my first mission seems to be accomplished :)
I didn't configure the server with the many performance optimizations that I used before, because I don't have the time currently and I need to change the configuration anyway when the final steps for switching to SDS are on the horizon. If there should be any performance problems in the coming days/weeks, that's because my server is busy with compressing approximately 450 GB of data and with parsing the whole blockchain with SDS in background. The new machine seems to do the job very well, as expected.
The good thing about my server being busy is: I can work on improvements for SteemWorld in the meantime. Even if the site might look completed to the average user, I tell you: There are still many things to improve and some really great features are still waiting in the pipeline ;)
The Transfer Search Tool now contains a summary row at the bottom:
Thanks to @daan for inspiring me with his post:
How to Calculate Your Drugwars Investments and Returns Using Steemworld + Spreadsheet
The text size of the account operation's data is now being adjusted based on the level (relative deepness) of the contained sub data:
I'm not fully satisfied yet, but at least are the custom_json's a bit better readable now. More optimizations will come when switching to the planned responsive layout.
Further text size and alignment adjustments are on the horizon:
A special thanks goes to @louis88 for detecting a potential security risk regarding XSS attacks with
custom_json operations. Even if there was no way to attack a different account than the own on SteemWorld, it's good to have that fixed now.
each of us to analyze and work with the Steem blockchain data in a simple and very efficient way (SQL and custom queries can be used too)parseBlock, parseTransaction, parseOperation and parseVirtualOperation methods within your script for each block)EN | What is SteemWorld?
-> Welcome to SteemWorld.org!
DE | Was ist SteemWorld?
-> Willkommen auf SteemWorld.org!
Positive thoughts create a positive world. It all begins with connecting our thoughts with emotions. What we focus on is what becomes powerful. We are the creators of our world.
Much love,