Multiple reactions from same user about yaga HOT 5 OPEN

Unfortunately this will probably never be possible since reactions are (in most use cases) connected to positive (or negative) points affecting the users score (which could then be gamed more easily). There are also checks in place (both in the controller logic and the database schema) to ensure that reactions are unique.

Together with your other issues it looks like you are trying to achieve a reaction system similar to GitHub or Discord (unlimited emoji reactions) while this plugin is more similar to the way Facebook handles reactions i think (fewer, unique reactions). A completely separate reaction plugin (that omits the aggregation by reaction type in profiles) would probably be needed here.

from yaga.

Yes we're trying to achieve a reaction system similar to Github and Discord.

For adding multiple reactions - I'm only refering to adding of one type of reaction per user. So in other words, I couldn't "game" the system by adding 10 likes to a post. I'd only be able to add 1 like, 1 heart, etc. Exactly as Github and Discord does.

Also you can't really "game" the system much this way because aren't the pointed calculated based on other people's reactions to your posts? That seems logical, rather than reacting to your own posts.

It also makes sense that you can gain points on multiple reactions on the same post - for example, if someone finds your post both Insightful and Funny you should be able to earn points on both.

Even if this is still problematic, for those that aren't that interested in awarding badges based on reaction points I would rather have the ability to add multiple reactions than be limited to just one.

from yaga.

I'll think about adding a switch for this. It would require database changes however (a utility/structure migration) since there is currently a UNIQUE index in place that prevents multiple reactions being inserted by the same user. This used to be a problem when spam clicking reactions so I'm kind of hesitant to completely remove it again.

from yaga.

This used to be a problem when spam clicking reactions so I'm kind of hesitant to completely remove it again.

Should probably be a minor cooldown when clicking reactions, limited in JS. So wait 500ms or so before sending reactions by ajax. That way if user spammed clicked at least it won't flood server.

Validation check should be in place to make sure they aren't adding reaction of the same type. I dunno how the toggling is done internally though.

from yaga.

Validation checks like this have always been in place. This is more of an issue with race conditions caused by laggy (mobile) connections and users trying to quickly remove a reaction they made mistakenly for example. Throttling/debouncing doesn't really help here. The backend should reject invalid entries like this in any case which is exactly what database constraints are for.

To ensure correctness the index would need to be extended to (InsertUserID, ParentID, ParentType, ActionID)

from yaga.