Skip to content

Showcase voting: vote on the best post and announce the result after 3 days #127

Description

@wiktoriavh

Why

Reactions only show a post's popularity. An explicit vote lets the community pick the best showcase post.

Acceptance Criteria

  • The bot posts a message asking members to vote on the best showcase post.
  • Members can vote from that message.
  • After 3 days the bot posts the result.
  • Results are sorted by votes, then by thumbs up.
  • The sorting logic is covered by unit tests.

Open Questions

  • What voting mechanism is used (buttons, select menu, poll)?
  • Can members vote for their own post?
  • Can members change their vote?
  • How are the votes stored so they survive a bot restart?
  • How are ties handled?

Out of Scope

  • Assigning roles (separate child issue).
  • Additional ranking criteria (separate child issue).

Activity

  1. michal-skraburski commented on Oct 10, 2026

    @michal-skraburski
    Contributor

    Answering open questions

    • Each post will have a reaction appended by the bot, the users then can click on it to vote for that project.
    • Members can vote for their own post, but it won't be counted towards the total
    • Members can't directly influence their vote count.
    • Discord should be used as the source of truth of the count, therefore the posts are recalled from discordjs if cache not present, or not uptodate, and each post is ranked.
    • Ties should be broken into 1st, 2nd, 3rd via time used as a tie breaker. e.g. equally rated items, first item should be granted priority.
  2. wiktoriavh commented on Oct 31, 2026

    @wiktoriavh
    MemberAuthor

    @michal-skraburski
    Here are my thougths, before I go into your suggestions:

    • we have the digest now, we can use that and put voting on top of it, adding reactions to it. Each post in the digest will have an emoji attached, so users know which reaction to choose.
    • I think the easiest is, it we allow users to vote for their own posts. It is something I have seen in others as well. Unless it will really skew things. The question is about: is it worth putting in the effort now, or will it just not be an issue?
    • yes, they can change their vote at any point before the result it revealed.
    • We should be using reactions. A bot restart will not remove this information from discord directly. when it is time to count the result, the count on each reaction will be summed - 1. -1 because the bot added a reaction as a starting point.
    • I would say it should be sorted by vote count and alphabetically. if they share the same space, they can both be on the Nth place.

    The announcement of the winners, will show the full result of all posts, but divided into the 1-3 place and then the rest. So it would look like this maybe:

    The best voted posts are:
    🥇 Foo
    🥈 Bar
    🥉 Zoo

    Honorable Mentions:
    🏅 Zar
    🏅 Top
    🏅 Bof

    Same role will be tagged as the one for the digest. And the announcement will happen 3 days after the digest was posted. Same cron job can be maybe used just with +3 days. Maybe there are edge cases? Unsure right now. Not important enough as of now.


    Now answering your suggestions, we had some similar ideas:

    Each post will have a reaction appended by the bot, the users then can click on it to vote for that project.

    Do you mean on the post itself? That would be lost IMO; since the idea is to bring awareness to the posts.

    Members can vote for their own post, but it won't be counted towards the total

    Generally yeah, but the question is how much more effort is this compared to what we gain from it? If the effort is high for a small gain, might not be worth putting effort into it now.

    Members can't directly influence their vote count.

    How do you mean that? That they cannot change their vote? How so?

    Discord should be used as the source of truth of the count, therefore the posts are recalled from discordjs if cache not present, or not uptodate, and each post is ranked.

    Yes, using discord as the truth here makes total sense. I don't think we even need a cache at all.

    Ties should be broken into 1st, 2nd, 3rd via time used as a tie breaker. e.g. equally rated items, first item should be granted priority.

    So if two posts share the same vote count, they should be sorted by who posted theirs first?

  3. michal-skraburski commented on Nov 6, 2026

    @michal-skraburski
    Contributor

    I believe I originally misunderstood the point of this feature -- rereading through it now I understand.
    Just to reiterate incase I got it wrong: You want to implement a separate way of voting on posts, so instead of reactions which we already use from feature 1/4 issue #126, we allow users to run a command of some kind (or some other method) to vote on a post. This vote is one time across multiple posts, so a user can only vote for one post. This is different from the digest, and therefore may even require a different channel outlet. It shows which post is the best out of all of them, instead of how popular a post was.

    Looking at this issue, I feel almost as if its redundant and it would be underused, unless we advertised. It feels a lot like a solution for a problem that doesn't exist, yet. I'm happy to implement this, however I feel it is a lot of effort for a low amount of gain.

    In terms of implementation, I believe this will require more than just reaction based voting, unless we revisit 1, therefore it will need to be some kind of slash command where the voter goes into the post and writes /vote and passes through a few checks such as whether they have already voted (otherwise this wouldn't be any different from a popularity contest feat. 1/4). This also means it'll require the database and the bot to be online at the time of the vote. We also should be tracking what showcase posts the authors have made to leverage the relationship between votes and their posts. Then when the digest occurs, we can advertise a voting contest and release an update 3 days after (assuming votes were made). When the voting has concluded, all data is wiped.

    Going over your questions, yes we have a lot of similar ideas:

    Each post will have a reaction appended by the bot, the users then can click on it to vote for that project.

    Do you mean on the post itself? That would be lost IMO; since the idea is to bring awareness to the posts.

    Yes, I did mean that initially, before I realised how Discord forum posts really worked, there's a configured dedicated button for a specific reaction which we filter by in the bot. This means my suggestion was made redundant. 1

    However this still has a place in the scenario you do not want to track any data, in which case we'll have to run a stateless check whether the user has already voted for a post within the current showcase digest period, then remove the previous check and keep the new vote. The bot will then append a reaction to each forum post for ease of voting.

    Members can vote for their own post, but it won't be counted towards the total

    Generally yeah, but the question is how much more effort is this compared to what we gain from it? If the effort is high for a small gain, might not be worth putting effort into it now.

    I don't think it would be that difficult to apply a check whether the user voting for this post is actually the author of the post. I also don't see anything wrong with letting them vote for it anyway, since the voting in my view should be unique and one time per showcase voting session.

    Members can't directly influence their vote count.

    How do you mean that? That they cannot change their vote? How so?

    This suggestion is a repeat of "Members can vote for their own post, but it won't be counted towards the total" -- I apologise.

    Ties should be broken into 1st, 2nd, 3rd via time used as a tie breaker. e.g. equally rated items, first item should be granted priority.

    So if two posts share the same vote count, they should be sorted by who posted theirs first?

    Correct. We need some kind of tiebreaker -- we can change this out to how popular the posts are, the more popular post is prioritised, if they are still tied then we use the time snowflake to break the final tie.

  4. michal-skraburski commented on Nov 6, 2026

    @michal-skraburski
    Contributor

    Corrected via call, we discussed that the /vote is overkill and that we should proceed with a reaction-based system.
    Differing from my suggestion, we will provide an emoji of some kind to each post highlighted in the biweekly showcase-digest. Users will then select the emoji pre appended to the post and select the post they wish to vote for that way. A post is ranked by how many votes it has, and the voting process is finalised 3 days after it is started. A new embed will be printed showcasing who won in this fashion:

    The best voted posts are:
    🥇 Foo
    🥈 Bar
    🥉 Zoo
    
    Honorable Mentions:
    🏅 Zar
    🏅 Top
    🏅 Bof
    
    Image
  5. wiktoriavh commented on Nov 7, 2026

    @wiktoriavh
    MemberAuthor

    If it is possible to do that without a databas, we should attempt that. If not, then introduce a new table for it.

  6. added
    triagedWhen an issue was triaged by the owner and given the green light for implementation.
    on Nov 7, 2026
  7. added a commit that references this issue on Nov 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    triagedWhen an issue was triaged by the owner and given the green light for implementation.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions