You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 11, 2024. It is now read-only.
There should be a parallel routing and message handling pipeline for emoji reactions. Both Slack and RocketChat fully support reactions.
Alternatively, we could expand our internal representation of an incoming message to also handle a reaction? One issue with this is that reactions are a much simpler message type, and yet also support both ReactionAdded and ReactionRemoved Events. As such, I think we would be better served by just having a different router object entirely.
Maybe orthogonal to this effort, we should make it much easier to attach a reaction to message as part of a response to a message. I am finding that in popular channels, having to respond inline, or even in a thread, is much more disruptive than being able to simply add a reaction.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There should be a parallel routing and message handling pipeline for emoji reactions. Both Slack and RocketChat fully support reactions.
Alternatively, we could expand our internal representation of an incoming message to also handle a reaction? One issue with this is that reactions are a much simpler message type, and yet also support both ReactionAdded and ReactionRemoved Events. As such, I think we would be better served by just having a different router object entirely.
Maybe orthogonal to this effort, we should make it much easier to attach a reaction to message as part of a response to a message. I am finding that in popular channels, having to respond inline, or even in a thread, is much more disruptive than being able to simply add a reaction.
The text was updated successfully, but these errors were encountered: