SteemWorld ~ Weekly Support ~ #12
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
Just some thoughts...
I'm still working on the improved Posts Overview and I hope that it will be ready to be used in the coming days. As always, when diving into a new development, there come a lot of new ideas to my mind and there are often a few things showing up which need to be solved in a better way. I am no 'never touch a running system' guy and do my best to restructure and optimize my code on a regular basis.
Such actions can take days without having any relevant, measurable changes for the users, but it's very important for developers to regularly take a look at the whole source, because not doing so can take away the motivation for wanting to care about the product in future. Since I'm the only one who is working on the code, I'm very flexible to do so, of course.
Keep in mind that most problems, which have not been taken care of in the past, will come back to you and may hit you hard at some point in future.
Auto-votes for old posts?
I receive many votes when I edit old (already paid out) posts, so there seems to be an auto-voting service active that does not check the posts payout date. Even more strange is the fact that I get votes from people who already voted on these posts before. I don't know which service you are using, but please do inform the developer about this. Thanks!
Posts now in tabs separated by status
You can choose to search for text in the posts title, body or both:
The drop-down box in the right contains all of your recently used tags for being able to easily add them to the current search criteria:
You can also search in a given date range:
Instead of having to scroll down the whole feed it is now possible to set the limit to 100 posts with one click:
Currently only the last 100 posts
As long as my new web service is under development and the posts are still being loaded from the Steem RPC nodes, there is a limit of 100 posts for each tab. So keep in mind, when you use the search tab, it will currently only search within the last 100 posts. Blockchains are great for storing data permanently, but loading the data and executing complex queries isn't possible without building a separate database or node API, that has been optimized exactly for the required tasks.
Filter for 'Custom JSON' operations
A few people contacted me lately, because they are playing Steem Monsters a lot and their Account Operations overview is filled with many 'Custom JSON' ops, which makes it nearly impossible to have a good overview of all the other operations, therefore I added a new op filter:
Warnings for special account events
We now get informed when a Powerdown has been started for our account.
Thanks to @double-u for the idea ;)
In the making
- Web service for loading the data in a more efficient way
- Different views in the Posts Overview
- Improved Coming Curation Rewards overview
- RC costs calculation
In my last post I mentioned:
Since the RPC nodes do no longer synchronize/return the account history and main account data in real time, I need to think about building and implementing a better solution. Maybe I can parse and store all blockchain data on one of my servers without having to rely on public node requests from the clients in future. I already do parse all blocks for some features on SteemWorld, but I do not have a solution for the account history yet. Would be great to store also the virtual operations, because that would enable me to have kind of a public node for my services without having to fulfil the huge hardware requirements for running a full steemd instance.
I will take a look at Steemit's SBDS (Steem Blockchain Data Service), because I think it could be capable of exactly what I need. I prefer to work with SQLite as it is really fast on SSD and requires no additional database service working in background. As I stated before, in my opinion it would be possible to deploy kind of an own Full-API Service on a 16 GB RAM machine with enough SSD memory available. That would be much cheaper than running steemd and is the only solution I can think of given my current monthly earnings.
I've decided to build my own solution (web service) to be more flexible now and in future. This will take a few weeks at least, but it will enable me to bring SteemWorld to the next level.
In the coming days there might happen an outage for some features on SteemWorld, because I need to execute a full re-indexing of the whole blockchain. Especially mentions, incoming delegations, post/vote counters and transfer/delegation search may not work as expected for a few hours. In case you should be experiencing strange things in the coming days -> It's just a temporary outage and I will do my best to bring the services back as soon as possible.
Thanks to @isarmoewe for reporting the bug regarding the incorrect counters for new accounts ;)
EN | What is SteemWorld?
-> Welcome to SteemWorld.org!
DE | Was ist SteemWorld?
-> Willkommen auf SteemWorld.org!
Thank you for supporting my work!
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.