RE: Is there a problem with vote counting in hivemind?
There is definitely a problem with Steemit's Hivemind node.
I assume that this has to do with the caching that was introduced some time ago. Obviously the parameters need to be checked again to find a good balance between reducing the query intervals and keeping the data up to date.
But maybe the implementation of the caching algorithm is not ideal.
My API node (including Hivemind) is running with the current version, but I can't say at the moment whether caching takes place here. I have not yet dealt with the caching process.
From my point of view, it's only a problem because we still can't change the API node in the Condenser so that another node can be used. Although the DIP team has created the function, it is probably still the CORS settings that prevent access to a third-party API node and switch it back to the Steemit node (see "Note" in section "4. Setting up RPC Node" of the announcement article).
If the problem was fixed, we could use alternative nodes long ago and wouldn't have the problem.
Since I don't see what settings the Steemit team uses for caching, it's also not possible to find out which parameters might be causing the problems...
In any case, the situation is currently very unsatisfactory.
I was assuming the same thing, but I don't see any github activity after Dec. 4, so I'm not sure if Steemit's engineering team is aware? (although it would seem like they must be...)
Right, I was looking for a way to change the API setting in upvu, too, but didn't find one. 😞 Not sure why this hasn't been top-priority for Steemit, since it would reduce the load on their API node. Also not sure why upvu didn't implement it, since (IIRC) they were the team that implemented the code for condenser.
Anyway, I guess the only thing we can do is try to make sure that Steemit is aware of the issue. Given that their curators use the platform, I suppose they must be aware, but I haven't seen any acknowledgement. Hence, this post. 😉
I think they know about it. I assume that they are already experimenting with the parameters. That's why it might not necessarily be visible on Github. However, I don't (yet) really know what parameters there are to control the caching in Redis.
But, you are right, a short feedback would be helpful for everyone.
Looks like progress(?): remove cache or decrease ttl #328
I am still cautious. The code is probably not online yet.
Your request of the
total_voteswith a current post still shows differences:{"jsonrpc":"2.0", "method":"bridge.get_post", "params":["pennsif", "the-steem-news-29-february-2024-community-curators-for-march-announced"], "id":1}api.steemit.com: 322
api.moecki.online: 363
api.steemitdev.com: 363
Yeah, it's definitely not fixed yet, and not even merged into the master branch. I'm happy to see some evidence of activity, though.
TEAM 1
Congratulations! This comment has been upvoted through steemcurator04. We support quality posts , good comments anywhere and any tags. TEAM 1
Congratulations! This comment has been upvoted through steemcurator04. We support quality posts , good comments anywhere and any tags.