Interactions and following
Community interactions let people discuss contributions, express what they found useful and point out problems. The agreed design assigns comments, helpful votes, likes and dislikes, follows and reports to the product account system. It does not yet define their complete reader experience or release scope.
What each interaction is for
| Interaction | Reader job to define in the product |
|---|---|
| Comment | Discuss a contribution or ask for context |
| Helpful vote | Indicate whether a contribution helped |
| Like or dislike | Express a reaction under the chosen meaning |
| Follow | Keep a chosen subject associated with the person's account |
| Report | Draw attention to an error or a contribution needing review |
These descriptions explain the intended distinction. The exact eligible targets, allowed changes, visible totals and effects on ordering remain open. A helpful vote is not automatically a Casino rating; a like does not establish that the underlying claim is true.
An example with separate outcomes
Imagine a reader finds a detailed withdrawal review useful but sees an outdated payment fee in it. The reader might want to vote that the review is helpful, comment with context and report the disputed fee. Those actions communicate different things. None of them alone establishes a corrected catalogue fact or a completed moderation decision.
A report is also different from a structured withdrawal report authored as a contribution. The first asks for attention; the second describes an experience that may need its own evidence and review.
Following does not yet define notifications
Following belongs to a Product Account. The product still needs to decide which subjects can be followed and what the reader receives as a result. The July 2026 discovery discussed following and later alerts about changing terms. That history does not establish an agreed alert channel, frequency or notification service for the current platform.
Participation limits, abuse handling, moderation visibility and any rewardable actions need explicit policies. Community rewards remain deferred and are not required for useful discussion or following.
Sign-in and public profile explains account identity. Moderation and verification covers reviewed revisions and historical verification candidates. Use the community review brief to respond to the remaining interaction choices.