mattyg
Currently creating, opening, assigning quantifiers, and closing a period is a manual process that must all be done by an admin user. It might be valuable to try to reduce...
Here is all the info we have about the underlying bug in the discord app that necessitated #302 This ticket is just to keep track of it -- so that...
A setting to include a fake "honeypot" praise in each user's quantification to help identify "lazy" quantifiers. The "honeypot" should be designed to look like legitimate praise, except for the...
It would be great to have metrics on the amount of time it takes for a quantifier to complete their quantification assignments. They could be included in the exported csv...
Indicate that other quantifiers have "dismissed" this praise -- to surface to other quantifiers that perhaps this praise should be dismissed. From liviade on TEC discord: > something really really...
Currently, `assignQuantifiersDryRun` uses the following algorithm to assign quantifiers to available "bins" of praise: 1. Select all quantifiers, sorted in a "random" order 2. Loop over list, assigning each quantifier...
Consider adding a setting to specify that quantifiers should not be assigned to two simultaneous periods.
Consider novel ways to reduce the effects of "decision fatigue" on quantifiers. The current options: - add quantifiers to pool and: - decrease parameter `PRAISE_QUANTIFIERS_PER_PRAISE_RECEIVER` - decrease parameter `PRAISE_PER_QUANTIFIER` Feedback...
It may be valuable to let quantifiers mark praise as "too vague to quantify". Some ways we could use this information: - notify giver to request clarification - ignore score...
It might be valuable to display relevant parameters to active quantifiers, at least `PRAISE_QUANTIFY_DUPLICATE_PRAISE_PERCENTAGE` From a quantifier at the recent quantification review: > I wanted to make sure duplicates had...