FEP-9967: Polls

Feedback wanted: Functionality of Polls

@andre just tooted the following:

While developing the initial version of the #polls for #ActivityPub #WordPress plugin, I so often got reminded to the preamble words of @gancio from @lesion

“Building software means taking a stand, making decisions, choices. These choices start from a precise look at reality, from specific needs and ends implementing specific features, choose default values, simplify some flow and patterns while making difficult others.”

It’s just a tiny poll plugin, but there are still decisions to be made: For example, when to reveal the poll vote counts, to whom, and when to reset the vote counts (e.g. when changing the type from single choice to multiple).

There are many flow patterns that I don’t consider worth striving for. Please help me by leaving some comments on the scenarios you can imagine.

For example Mastodon always extends the expiration date when editing a poll, even if the poll has already ended. Is this scenario of extending a poll as long as it suits the poll creator anything I should worry about?

Another example: Mastodon allows you to reveal results of a poll by another person. Immediately after you did that, I does not allow you to vote, but on page reload you may.

Should one be allowed to vote on own polls?

How important is protecting anonymity of voters? Is not providing UI or APIs enough, or should it be almost impossible to get the voters choices from the database?

I wonder, one could hash the remote actors who replied, one could even salt that hash differently for each poll. But this would maybe make it harder in the future to prevent bad actors and spamming of polls.

3 Likes