Up to now the Discourse Reactions plugin only allows a single reaction to count as a like for the purposes of topic rankings and badge granting.
Now that reactions have become an important way site members interact with posts, we are changing this paradigm. All reactions will count as a like except for those specifically excluded via a deny list. By default, only the reaction does not count as a like.
As part of this change, sites that have been using reactions will find that topic rankings and badge granting will get an adjustment to more accurately reflect engagement. It will not be possible to opt out except to add all reactions you do don’t want to count as a like to the deny list.
Note that by default, the like reaction is but it can be changed to or whatever reaction works best for your community. You will not want to change this again once your site becomes established. Historical Like records will not be changed if this setting is altered. It’s best to set it once and forget it.
We have now rolled this on Meta, and soon we will roll it out to all sites using reactions.
Backfilling logic is initially disabled by the discourse_reactions_like_sync_enabled site setting. In a few weeks, we will remove this setting and run an initial migration is included to backfill PostAction records for reactions which are not the discourse_reactions_reaction_for_like (by default this is set to ) and not on the discourse_reactions_excluded_from_like list. It is not recommended to change this setting after your site is already established, as we will not do historical cleanup. Some communities have hundreds of thousands if not millions of Like records.
Any time discourse_reactions_excluded_from_like is changed, we will correct history with a background job. Any reactions that are added to the deny list will have their matching PostAction records destroyed, and any reactions removed from the deny list will have matching PostAction records created. We also correct history every hour in a scheduled job if discourse_reactions_like_sync_enabled is turned on.
There is no way to opt out of this – if you don’t want any reactions to count as a Like except the default discourse_reactions_reaction_for_like, then you should add all of your discourse_reactions_enabled_reactions to the discourse_reactions_excluded_from_like list.
On most sites I visit it would not imply a like but that one has seen the post or is reviewing the content in the post. Often this is used on technical sites were it may take a few hours to months to review (think proving a theorem or validating research from a paper).
Unless it’s added to discourse_reactions_excluded_from_like it will count as a Like. Though sites without Reactions enabled have traditionally used the heart to convey a similar thing, so it could work either included/excluded depending on how stringent you wanted to be.
That is the problem. Most users I know would not expect to be counted as a like. IMO should be the other way. should default to not being counted as a like and only be counted as a like if changed.
Maybe it should not be considered a reaction but a reply as it is not a positive or negative reaction. Think of it as a reply that does not trigger a notification but lets others know that one has seen the post.
If I knew that would eventually be considered as a positive reaction I never would have suggested the use .
Ah, I reset the time window again back to 10 minutes (after that time you can’t remove a Like or Reaction), so I think that’s expected. But keep your eye out for anything weird happening with another post when you try it again.
And if you click on the Reactions on the left, that brings up the info box for them rather than just the Likes.
We also correct history every hour in a scheduled job if discourse_reactions_like_sync_enabled is turned on.
So if I want to have the history corrected, I enable this setting and disable it after 2-3 hours? And new reactions will get their correct sync anyway?
Yes this is correct, there is a job that runs every hour to correct history. Alternatively you can just wait a few weeks for us to more widely enable this, at which point we will run a data migration to backfill the history.
I’m not sure I understand the screenshots and the report… what do you mean when you say reactions “count both the reaction and a like or they only count as a like when they shouldn’t”? Are you just referring to how reactions and likes appear in the user interface?
There’s actually a third behaviour here on Meta, reactions besides don’t exist!
I don’t understand… on meta I see reactions and heart, and even in your screenshot I can see reactions?
Thanks for this change. This is something that I really missed.
I’ve enabled the discourse_reactions_like_sync_enabled 10 days ago. Now, it makes all related badge, etc… available to rename it to reaction? I mean for example there are the Gives back, Good Topic or other likes related badges now should be named reactions in there description and the First Like should be first reaction and the first reaction badge should be removed or vica versa because now it means the same.
Of course these are only if the reactions plugin installed.
Same thing with Discourse Gamification, now it can score the reactions too so the likes rate will means reactions.
Etc… Probably there are more places where this can be confuse.
Thanks, Don! I agree updating the gamification topic is probably a good idea, so that it more accurately explains how it works. Also any documentation topics on meta about the badge system.
But I don’t know if it’s worth tying ourselves in knots changing the language describing likes and throughout the discourse interface, like on the badges page, users page, user profiles, etc etc. Most people using sites won’t really know the difference between a like and reaction, or which reactions don’t cout as likes etc. So I’d suggest we just leave it as it is. In these places, and like just includes likes and positive reactions, and excludes any reactions in the discourse reactions excluded from like admin setting.
Thanks for the answer! Yeah, I agree with you. But unfortunately I made lot of time to educate our Community what is the difference between and and other reactions. So I have to do this step to rename it everywhere. I don’t use negative reactions so every reaction counts as like. There are lots of places e.g. documentation about trust levels, gamification and other… The like rate limit TL site settings and the related system modals if the user reach these limit now means reactions rate limit and also the topic list item icon and other notifications about likes should use for example the discourse-emojis icon. But this is only for me the case and I agree it isn’t necessary to change in core.
That’s good feedback… you are probably not alone here. What do you suggest we change it to?
Also, reactions is not in core discourse so the language we use has to also accommodate sites that don’t have reactions. I think for now we’ll keep it but eventually if reactions makes it into core discourse we can just replace all references to “like” to “reaction” and ignore that there might be some reactions that have been deemed to be negative and are excluded from counting as likes.