Skip to content
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

Implement removal of reactions #154

Closed
Cadair opened this issue Jul 5, 2019 · 3 comments · Fixed by #485
Closed

Implement removal of reactions #154

Cadair opened this issue Jul 5, 2019 · 3 comments · Fixed by #485
Labels
T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements.

Comments

@Cadair
Copy link
Collaborator

Cadair commented Jul 5, 2019

Currently we add reactions in both directions but can't remove them across the bridge.

For matrix -> slack reaction removal, the issue is when we add the reaction to slack, the reactions.add slack API method doesn't return the ts of the reaction event. You would have to listen for the event to come in on the event stream.

For slack -> matrix removal, the issue is that the slack event reaction_removed also dosen't give you the ts of the reaction event, it gives you the ts of the parent event as well as the sender of the reaction and the key of the reaction. This therefore means we would have to use the not-finished-yet aggregations API to query synapse for the event ID that matched those parameters.

@Half-Shot
Copy link
Contributor

See also #131

@jaller94
Copy link
Contributor

jaller94 commented Sep 7, 2020

Where to find out more about the Aggregations API and has it been finished?

@auscompgeek
Copy link
Contributor

MSC2675 describes aggregations.

@jaller94 jaller94 added the T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements. label May 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants