Sending soft failed events to willing end clients #837
Labels
No labels
Bug
Cherry-picking
Database
Dependencies
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/Federation
Matrix/MSC
Matrix/Media
Meta
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Wont fix
old/ci/cd
old/rust
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: continuwuation/continuwuity#837
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
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.
Receiving soft-failed eventsto Sending soft failed events to willing end clients