-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing reaction events #174
Comments
While reaction events aren't yet parsed and turned into a nice Python class, they can be accessed as an UnknownEvent. |
@poljar Is this still the case? Was wondering if Mirage can add reactions in currently. |
It is, I'm still stuck in crypto rewrite limbo. |
For reference, sending a reaction is relatively easy even without explicit support async def send_reaction_to_room(
client: AsyncClient,
room_id: str,
message: str,
event: RoomMessage,
):
content = {
"m.relates_to": {
"rel_type": "m.annotation",
"event_id": event.event_id,
"key": message,
}
}
await client.room_send(
room_id,
"m.reaction",
content,
ignore_unverified_devices=True,
)
#--------------------
# ...
await send_reaction_to_room(client, room_id, "👀", event) |
@poljar Do you mind if this is something I take up? |
No, I don't mind at all. Contributions as always are welcome. |
Reopening since #252 is about stickers and not about |
Is it possible for nio to support m.reaction events? It would be nice to be able to have the bot react to messages as well as detect when users react to messages.
The text was updated successfully, but these errors were encountered: