Skip to content

Conversation

@robintown
Copy link
Member

I realized that these capabilities would need their own MSC separate from the actual sticky event MSC, and Timo has kindly gone and drafted one. Changing these experimental identifiers while they're still hot off the press.

I realized that these capabilities would need their own MSC separate from the actual sticky event MSC, and Timo has kindly gone and drafted one. Changing these experimental identifiers while they're still hot off the press.
@robintown robintown force-pushed the robin/sticky-event-caps branch from 6eb136a to ce90b06 Compare January 21, 2026 16:49
@sonarqubecloud
Copy link

Comment on lines -96 to -99
/**
* @experimental It is not recommended to rely on this existing - it can be removed without notice.
*/
MSC4354SendStickyEvent = "org.matrix.msc4354.send_sticky_event",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is interesting. We decided against it. It might make sense to revise this once we refactor the jssdk to properly mimic, that we have a new endpoint for sticky events now (due to the different response)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you thinking of delayed events? Sticky events only use a query parameter on the normal PUT /_matrix/client/v3/rooms/{roomId}/send/{eventType}/{txnId} endpoint as far as I can tell.

@robintown robintown merged commit ec20c7f into master Jan 21, 2026
5 checks passed
@robintown robintown deleted the robin/sticky-event-caps branch January 21, 2026 18:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants