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

chathistory: add chathistory-context tag #526

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

emersion
Copy link
Contributor

See discussion at #524 (comment)

@emersion emersion mentioned this pull request Jun 14, 2023
@slingamn
Copy link
Contributor

I support this! I would have relaxed "MUST immediately follow" to "MUST appear after", but the language here works for me as long as it's helpful to clients.

@emersion
Copy link
Contributor Author

The intent here is to allow clients to figure out which message is the parent of a context message. For instance, a client might want to populate a "parent_context" column in its DB, to retrieve all the context messages attached to a parent message when locally fetching history.

That said, with msgid tags, it should be possible to reconstruct the relationships client-side, at least for context messages that the client understands.

Is the mandated behavior an issue for server implementors?

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.

2 participants