Difference between revisions of "Flow/Server based 1-1 chat state"

Jump to navigation Jump to search
Line 18: Line 18:
# Clients are able to determine the MAM ID before they send the message
# Clients are able to determine the MAM ID before they send the message
# It's a good idea to keep the state after stream resumption
# It's a good idea to keep the state after stream resumption
# More message types need to be forked for incoming and outgoing messages, not just chat.
# More message types need to be forked for incoming and outgoing messages, not just chat (as it's currently done by the carbons XEP).
# Forked and forwarded messages should possible be queued when the receiving client is inactive (e.g. by means of CSI)
# Forked and forwarded messages should possible be queued when the receiving client is inactive (e.g. by means of CSI)


165

edits

Navigation menu