prevent the same person from upvoting or downvoting the same article more than once

[Thesephi]

No description provided.

[khanetor]

Maybe a solution is to keep track of who upvotes and who downvotes instead of the count?

[khanetor]

Also this may not be needed for the demo, because it would be a hassle to have to create many accounts for testing.
We can assume that a person will only vote once, while letting them vote many times.
We can ignore retracting a vote for now too.

[Thesephi]

• Agreed on the bit where we leave this for a future date for the sake of simple POC.
• Re. "creating many accounts for testing", NEAR has the sub-account mechanism where it's pretty simple to spin off multiple accounts from an existing account. We can even write a script for this :) We can stay logged in under many accounts on the same machine, so we can sign transactions under those many accounts.

[Thesephi]

Maybe a solution is to keep track of who upvotes and who downvotes instead of the count?

• Definitely will need a data structure to keep track of account IDs who have voted. Also, the same account cannot put both an upvote and a downvote :)
• Trivial question: should we still use the vote count as a number? If we keep the list of account IDs, we can retrieve the vote count dynamically & effortlessly, so probably will deprecate the use of vote count as a single number, right?

[khanetor]

Maybe a solution is to keep track of who upvotes and who downvotes instead of the count?

* Definitely will need a data structure to keep track of account IDs who have voted. Also, the same account cannot put both an upvote and a downvote :)

* Trivial question: should we still use the vote count as a number? If we keep the list of account IDs, we can retrieve the vote count dynamically & effortlessly, so probably will deprecate the use of vote count as a single number, right?

I would put the voter IDs in the backlog, and simply keep the vote count as numbers (upvotes and downvotes) for the moment.