Keep track of users using some sessions plugin. Use this information to prevent a user from suggesting the same add or cut multiple times. I think the most "practical" way to do this is to create a collection that holds deck._id, a user id, a card uuid, and a value for whether they've suggested an add, cut, or both for that card in that deck. Ideally these user sessions would persist between server reboot. I think potentially storing them in the database is fine, but I'm very open to other, better solutions if they exist.
Keep track of users using some sessions plugin. Use this information to prevent a user from suggesting the same add or cut multiple times. I think the most "practical" way to do this is to create a collection that holds deck._id, a user id, a card uuid, and a value for whether they've suggested an add, cut, or both for that card in that deck. Ideally these user sessions would persist between server reboot. I think potentially storing them in the database is fine, but I'm very open to other, better solutions if they exist.
See #3