New hard fork 24 is a bit breaking for https://hive.vote. We use hive RPC nodes for hive.vote to get the accounts, votes, and posts with the minimum latency. In v1.24.2 (new version of hived) all the votes and posts moved to the hivemind. Since we need the votes and posts, the only available option is to set up our private hivemind. But hivemind is a big database of ~600GB data which takes a few days to fully sync on a fast storage machine.
We can set up our hivemind instance and get the data we need. But we at https://hive.vote, don't need all of that data from hivemind. Actually, we only need the posts and votes from the past 7 days. So, the only option I can think of is, building our own database structure which is optimized for fast writes and reads and takes way less time to fully sync (I'd guess less than 30 minutes).
The Best Option
So, I will start building this new database structure and will share it with the community. I believe there are already a few projects like this but I'm sure those will require modifications and that requires reviewing all the code which takes time. And we are short on the time.
So let's build our own structure which will open up the opportunity to add more features to the website.
Of course, if you think you have the solution to our problem or can help us in any way, please comment below.
As I said, hf24 will break https://hive.vote. So we have to turn off all the services on 6 October until the new back-end product is ready.
I'm not sure how long it will take, but I will do my best to bring it back as soon as possible.
It seems an easy job but "don't judge a book by its cover". I'm sure it will beat me up.
On a side note: The time for hf24 may change again (unlikely but possible), so the maintenance time may change based on that.
Any amount of donations are much appreciated. https://hive.vote is free because of your kind supports.
Don't hesitate to leave your suggestions/feedback in the comments.
Thanks for your kindness ❤,