Sending soft failed events to willing end clients #837

Open
opened 2025-05-24 21:06:34 +00:00 by Jade · 1 comment
Owner

The tracking and based on previous conversations in the chat rooms.

I think the final conclusion was an account data setting for this to come down normal sync. I believe @nex is working on it

The tracking and based on previous conversations in the chat rooms. I think the final conclusion was an account data setting for this to come down normal sync. I believe @nex is working on it
Jade added the
Matrix/Client
label 2025-05-24 21:07:29 +00:00
Owner

This will likely happen in two parts, one will be sending down /sync, and the other will be exposing over /messages. I believe the former will be easier to add, but also, our syncv3 is already a little bit dodgy (see also: #779) and I want to avoid adding more complexity to it for the time being. Perhaps jumping straight to appservices for the time being would be the easiest and also of more use.

This will likely happen in two parts, one will be sending down /sync, and the other will be exposing over /messages. I believe the former will be easier to add, but also, our syncv3 is already a little bit dodgy (see also: #779) and I want to avoid adding more complexity to it for the time being. Perhaps jumping straight to appservices for the time being would be the easiest and also of more use.
nex added the
Enhancement
label 2025-05-24 21:55:39 +00:00
Jade added the
Matrix/Appservices
label 2025-05-24 22:29:57 +00:00
nex changed title from Receiving soft-failed events to Sending soft failed events to willing end clients 2025-05-27 02:47:31 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: continuwuation/continuwuity#837
No description provided.