Client Event System

[jazzz]

Problem

Currently Applications learn that they have been invited to a new group by watching for a boolean flag set on ContentData. This approach is brittle, and does not scale with added features.

Specifically: Currently it is required that a new Conversation always contains some content, or else no payload is passed back the to applications. MLS works differently and there is not guaranteed to be a content message, when a participant first joins the group.

In these cases its not clear how to pass data to applications.

Solution

A system that allows clients to notify applications of changes and updates from the Clients state. This includes:

• new conversations
• delivery receipts
• reliability failures.

Design Criteria:

• Positive Developer Experience
• Clear growth path - New events will likely be added - helpful to have a clear plan how those would be supported.

Features:

• Events + data can be passed to applications without requiring content

[jazzz]

Excited to see what your plan for this is @osmaczko.

[osmaczko]

Completed by #99, #106, #123, #125