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
I couldn't find another issue for this, so filing it here as a way to keep track.
It would be good if the Android app supported reactions in the same way the iOS app does them. In that app they're called tapbacks, also seen them called reactions, etc.
How iOS is doing them: a reaction emoji is sent as a text message with the emoji as the text, but additionally setting the emoji field on Data set to 1 (it's a fixed32 but being used as a boolean) and the reply_id on Data set to the message ID of the message being reacted to. (not to be confused with request_id)
In principle I don't see any reason this couldn't work with any random emoji, though copying the iOS list of options might be reasonable as well.
Relevant log output
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Contact Details
No response
Tell us your idea.
I couldn't find another issue for this, so filing it here as a way to keep track.
It would be good if the Android app supported reactions in the same way the iOS app does them. In that app they're called tapbacks, also seen them called reactions, etc.
How iOS is doing them: a reaction emoji is sent as a text message with the emoji as the text, but additionally setting the
emoji
field onData
set to 1 (it's a fixed32 but being used as a boolean) and thereply_id
onData
set to the message ID of the message being reacted to. (not to be confused withrequest_id
)In principle I don't see any reason this couldn't work with any random emoji, though copying the iOS list of options might be reasonable as well.
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: