Homeserver responds with `200 OK` to reaction removal, but requires ⪆ `PT4H` to remove the reaction.

[RokeJulianLockhart]

Description And Reproduction Of Problem

The effect for the user is as element-hq/element-web/issues/28249#issue-2600384194 describes. However, what is actually occurring is the server is informing the client that its request for reaction removal is successful, despite the server taking up to multiple hours to actually remove the reaction. This is erroneous.

Placement Rationale

1. I have reported this to @matrix-org, per element-web/issues/28249#issuecomment-2452332498 – a recommendation to do so by a developer of the Element client:

   The server says the redaction is successful with a 200 OK, so is not something a client can reliably detect or deal with.

   I suggest that you read the thread. It is adequately concise, and explains better than I am able to summarise.

2. I have reported this at this repository because orgs/matrix-org/repositories?type=source&q=server didn't return any better results in +2024-11-06.

[RokeJulianLockhart]

#2553 (comment)

@HarHarLinks, should this be transferred again, then? If so, having someone with permissions to would be assistive, else I'll have made an awful lot of duplicates.

[HarHarLinks]

I (as a community contributor) don't think there is a proper place to put it, I'm not even sure any of the contact points https://matrix.org/contact/ are appropriate - maybe the support contact. The maintainers of this repo however will not be able to help, as they are only concerned with the website.

It's possible yours is a matrix.org-specific issue but it might also be a synapse issue in which case you might have luck there.

[RokeJulianLockhart]

#2553 (comment)

@HarHarLinks, I have since tried those avenues, but it wasn't trivial:

1. I am unable to even join develop.element.io/#/room/#matrix:matrix.org, ¹ because I merely see an error modal:

   

   I have no idea of whether that's worth a separate bug, nor where, if so.

2. Regardless, luckily, joining #foundation-office:matrix.org ² worked, so I've posted develop.element.io/#/room/#foundation-office:matrix.org/$42n_Z8Qqdp5E9J8HlcT_q4EA6pgQC2GSiIDOhIvgE84.

3. I've also sent Message-Id: <ufm_5yuYwlMaQw8y9wqdkp__OSjImdJ5TGO4brRrHPiLUIlZdq6YBUrTBWFFbWQLX0gpHpJ43LIvimtLLjaHo4Obl9fgYRVieGDsaB-_Ki8=@pm.me> to support@matrix.org (SUP-3703). ³

It's possible yours is a matrix.org-specific issue, but it might also be a Synapse issue, in which case you might have luck there.

I've attempted to ask at #synapse:matrix.org, ⁴ but it fails with the same error. Should I just file an issue at synapse/issues/new?template=BUG_REPORT.yml, to have it triaged...?

Footnotes

1. 3bcead0d65d59a193e22cbea69b1629d71c08bc3/content/contact.md?plain=1#L6C13-L6C31 ↩

2. 3bcead0d65d59a193e22cbea69b1629d71c08bc3/content/contact.md?plain=1#L6C122-L6C151 ↩

3. 3bcead0d65d59a193e22cbea69b1629d71c08bc3/content/contact.md?plain=1#L14C4-L14C22 ↩

4. element-hq/synapse/blob/9cf0ef9c70c0f2b93f4056d6273f130e7a75a201/.github/ISSUE_TEMPLATE.md?plain=1#L1C52-L1C71 ↩

[RokeJulianLockhart]

Transferred to element-hq/synapse/issues/18987. ¹

Footnotes

1. develop.element.io/#/room/#foundation-office:matrix.org/$Yy8KCk6F9dW3D8qA1QESZdItgT7tS4zcCY0_QJ_nwqs ↩