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

Spec how N+1 replies work in terms of fallback #372

Closed
turt2live opened this issue Sep 5, 2018 · 5 comments · Fixed by #1994
Closed

Spec how N+1 replies work in terms of fallback #372

turt2live opened this issue Sep 5, 2018 · 5 comments · Fixed by #1994
Labels
A-Client-Server Issues affecting the CS API clarification An area where the expected behaviour is understood, but the spec could do with being more explicit

Comments

@turt2live
Copy link
Member

No description provided.

@turt2live turt2live added clarification An area where the expected behaviour is understood, but the spec could do with being more explicit A-Client-Server Issues affecting the CS API labels Sep 5, 2018
@richvdh richvdh transferred this issue from matrix-org/matrix-spec-proposals Mar 1, 2022
@Cadair
Copy link
Contributor

Cadair commented Mar 15, 2023

Am I correct in thinking that the way these work is that you just fall back to the most recent message you are replying to?

@richvdh
Copy link
Member

richvdh commented Mar 15, 2023

I don't even know what N+1 replies are

@Cadair
Copy link
Contributor

Cadair commented Mar 15, 2023

I was assuming it was talking about replies to replies (to replies (...))

@turt2live
Copy link
Member Author

Yea, this is replies to replies [to replies [...]].

The question is mostly what you're supposed to stick in the <mx-reply> (and markdown-ish quote block): some clients believe the whole chain should be there, but others disagree. We mostly just need to pick something that makes sense and do that.

It's possible this needs an MSC.

@Cadair
Copy link
Contributor

Cadair commented Mar 15, 2023

Given the open MSCs about ripping out the fallbacks completely I think I will leave this one to be overtaken by events...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Client-Server Issues affecting the CS API clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants