17 Jul
2024
17 Jul
'24
2:51 a.m.
hi
On Mon, Jul 15, 2024, at 23:17, Tim Henkes wrote:
Voting (and polls) are actually something I thought about beforehand and
wanted to have them covered by this XEP. My idea is that rules like the
ones you mentioned are enforced by the voting bot and not the XEP. The
XEP simply gives you a way to trigger an action - the voting bot would
be the one to "execute" the action, including check whether the same
person is trying to vote again and block that/make it a correction
instead etc.
Does that sound okay?
Actually no, sounds like it does not cover the most basic things i would expect from a
voting functionality.
1. It should be possible for every user to create a vote, without the help of bots
2. The results should be able to be displayed live, not only at the end of a vote
3. Vote Correction, Voting for multiple options, etc should be a thing
4. Probably many other simple features other messengers provide with votes
When you propose that this XEP should be used for voting, and that rules are enforced by a
bot, what i see is
1. In a MUC with 500 users, people spamming the message archive with responses which
everyone else will then download, although they cannot display them because they have no
idea about the rules of the vote, because only the bot knows what counts
2. No client even has an idea that this is a vote, can only be guessed from the text by
the user, not programmatically by the client, so no custom UI possible.
3. Answer from the bot is undefined, will it be simply the result as text message? Again
not possible to do any kind of UI.
If this really should be used for voting, the XEP does not add anything over what we have
today.
We currently can send whole XEP-0004 dataforms with every message and its well defined
and implemented how dataforms are to be filled out and submitted. The actions part of the
XEP is in essence a dataform with a single list field option.
Regards
Philipp