Vote irregularities

I've been playing with the voting system on a couple of lists (this one included).
There are some weird behaviours I've noticed:
votes are frequently not immediately reflected - a page reload is required
some votes display as: 0 0 You dislike it (cancel)
Here we see I've voted on a message, but the counts are still zero up and zero down.
I just down-voted one of my posts as a test, and nothing changed in the page to reflect the vote. Often it takes multiple clicks, sometimes a page reload.
Browser console shows voting generates a 200 response to a POST method, but the JSON confuses me:
like 0 dislike 0 html '\n\n <form method="post" class="likeform"\n action="/archives/list/talk@lists.domain.tld/message/IK6WH4IQPZXOG3CIFV4CJGOKVFARGXA5/vote">\n <input type="hidden" name="csrfmiddlewaretoken" value="***">\n \n\t\t\n\t\t\t<a class="youlike vote "\n\t\t\thref="#like" data-vote="1" aria-label="Like thread">\n\t\t\t\t\t<i class="fa fa-thumbs-o-up"></i> 0\n\t\t\t</a>\n\t\t\t<a class="youdislike vote"\n\t\t\thref="#dislike" data-vote="-1" aria-label="Dislike thread">\n\t\t\t\t<i class="fa fa-thumbs-o-down"></i> 0\n\t\t\t</a>\n\t\t\n \n\n </form>\n'
The uwsgi.log file entry for that vote is:
[pid: 4010303|app: 0|req: 552908/575956] 127.0.0.1 () {66 vars in 1374 bytes} [Sun Aug 10 02:28:21 2025] POST /archives/list/talk@lists.domain.tld/message/IK6WH4IQPZXOG3CIFV4CJGOKVFARGXA5/vote => generated 696 bytes in 376 msecs (HTTP/1.1 200) 9 headers in 394 bytes (1 switches on core 1)
Following the Permalink beside the voting options loads the specific message with no votes showing.
Ctrl+F5 shows no votes. Re-casting vote and reloading shows no votes.
Clicking "Back to thread" shows my message and:
0 0 You dislike it (cancel)
I don't think I've ever seen reliable voting on any MM3 site, including this one (I don't think I've seen zero / zero You {like|dislike} it (cancel) here, but multiple vote attempts to see the results is not unusual).
Searching the archive shows something from ~6-7 years ago where caching was modified, seems relevant but nothing since.
Am I alone in this, or is the feature so unused that nobody else noticed this?

Ron writes:
I've been playing with the voting system on a couple of lists (this one included). There are some weird behaviours I've noticed:
I don't know if there is anybody left who is expert on that.
HyperKitty was developed by Red Hat or Fedora personnel, and has not had much if any further development attention for at least five years since they withdrew support. The voting was a feature they wanted, not something that was demanded by the Mailman community IIRC. As an archiver, HyperKitty just works, and the issues I remember have all concerned messages not making it to the archives, performance, or text indexing.
Am I alone in this, or is the feature so unused that nobody else noticed this?
FWIW, I never paid any attention to the voting feature and I don't know anyone who does. I'm sure there are communities that do. Perhaps someone who does can provide more input. It's a feature we distribute, so we should give it some love, but if we have no expertise, it could take a while.
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan
participants (2)
-
Ron
-
Stephen J. Turnbull