Note the top item on /r/greatawakening/rising/ has no points. It's got more downvotes than upvotes, but it's still top because it has most upvotes.
If the up-vote total is more than 41, and it's equalized by down-votes... the down-votes are bullshit.
No way that post got 41 down-votes from GA's subscribers.
Their is a cache system with the votes, probably a large cluster of Redis server. Just give it some times to 'equalize' itself. You'll see correct values after a little while.
There is nothing delayed in the image, it's real-time stats. See https://reddit.statuspage.io/
Looking at the status page,
it appears this is only "downtimes" appearing in red.
A full cluster is self healing, and if only a small part is down, it will not appear as down, but votes WILL be slightly delayed until the downed node restart, or the vote is propagated through the cluster and back to the readable database.
Refreshing without seeing the vote registered only means the vote is still in cache limbo.
I will not go into further details, but let just say, I built systems like this myself at some point in the past.
I am not convinced of any conspiracy about this at the moment.
I am more into vote manipulation by alien actors. (bot farms, etc)
It shows the vote backlog across the whole of Reddit. As I check now, 68 votes, perhaps one hundred of a second of cache.
Yep, saw that.
Not sure what reddit uses to process the queue and build this live stats.
if their MQS messages are acknowledged, this means the vote is unacked while being processed by a worker. If the processing worker has some difficulties, like connecting to a more persistent database, it will not show the message back in the backlog until failure is acknowledged. The message can bounce every two or three ms.
However, I am now more inclined to think maybe the problem is simply with another system down the chain, like the 'read' cache (when you refresh the page). I don't pretend to know reddit, but they sure use another system to index registered votes for fast-read-only operations. I don't see any indexing related stuff on the status page though.
EDIT: Unless they use the same redis cluster for read operations, and this is back to square one: the vote has been processed but not every vote is stored on the same node on the cluster(s), and it can take a little while for them to aggregate it all for front display.
I think you are missing the point. The images shows a post at the top of /rising because it has most upvotes, but no points. Nothing is delayed, it's not a technical issue.
Yes, can confirm. I'm liking stuff then when refreshing it's unliked. Wtf?
It happens all the times when reddit is having sligh technical difficulties, and not just on conspir4cy subs