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

Replies: Have a key for the reply text itself #350

Closed
turt2live opened this issue Aug 20, 2018 · 2 comments · Fixed by #1994
Closed

Replies: Have a key for the reply text itself #350

turt2live opened this issue Aug 20, 2018 · 2 comments · Fixed by #1994
Labels
A-Client-Server Issues affecting the CS API enhancement A suggestion for a relatively simple improvement to the protocol

Comments

@turt2live
Copy link
Member

Currently people who wish to use replies need to parse either the fallback out of the reply or parse some HTML. In retrospect, the reply should probably have a key for the text that is being replied rather than forcing people to pick which key to throw parsing on.

For html-enabled clients this isn't really a problem, however for stuff like bridges the replies become hard to parse.

@turt2live turt2live added the enhancement A suggestion for a relatively simple improvement to the protocol label Aug 20, 2018
@Half-Shot
Copy link
Contributor

Oh huh, I was about to look for this. Thank you!

@Half-Shot
Copy link
Contributor

The other option here is to throw away the fallback and have non-compliant clients just show the reply text in the body, which would be space saving and avoid fallback screwups.

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 enhancement A suggestion for a relatively simple improvement to the protocol
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants