Package-level declarations

This use case will add a member(s) to a given conversation.

This use case will add a service to a given conversation.

Checks if the conversation invite code is valid

Checks whether the self user is allowed to leave the given group conversation.

Checks whether the active one-to-one conversation with otherUserId is ready to be opened. Proteus conversations are ready once present locally. MLS conversations are ready only when their group exists in Core Crypto.

This use case will clear all messages from a conversation and notify other clients, using the self conversation.

Use case for clearing and drop orphaned typing indicators

Operation that fetches all known users which are not a part of a given conversation conversationId

This use case that get Conversation.ProtocolInfo for a specific conversation.

This use case will observe and return the conversation list for the current user. Prefer using ObserveConversationListDetailsUseCase instead, since is performance efficient, relying on sql views.

UseCase for getting once the amount of unread events (all: messages, pings, missed calls, etc.) in a specific conversation.

This use case will observe and return the conversation model for a specific conversation.

Operation that returns Conversation data for the one-to-one conversation with specific UserId.

Operation that creates one-to-one Conversation with specific UserId (only if it is absent in local DB) and returns Conversation data.

This use case will observe and return a flow of paginated searched conversation details with last message and unread events counts.

Searches joined groups and channels, loading members in batches for each page.

Operation that indicates if we have one-o-one Conversation with specific UserId.

Use case to check whether the self user has viewer access to a drive conversation.

Use case for joining a conversation via a code invite code. the param can be obtained from the deep link

Joins pending MLS conversations by external commit after this client may have been left out of MLS groups: it ran out of key packages, or it registered its MLS client after conversations were migrated to MLS.

Use case to immediately update the conversation read date in the local database

This usecase returns a list of members to mention for a given conversation based on a search done with searchQuery The result should ordered respecting this order of priorities:

This use case will migrate a given conversation to use the MLS protocol

Internal use case to repair conversations with faulty MLS keys based on known faulty keys per domain. This is intended to be run once after an app update that includes the fix for the faulty keys.

Used by the UI to notify Kalium that a conversation is open. It's useful so Kalium can lazily perform update operations and make sure that the conversation is up-to-date when the user opens it.

UseCase for observing the count of archived conversations that have unread events (e.g., messages, pings, missed calls). The result is presented as a continuous flow, updating whenever the count changes.

This use case will observe and return the conversation details for a specific conversation.

Use case that check if self user is able to interact in conversation.

This use case will observe and return the list of conversation details for the current user.

This use case will observe and return the list of conversation details for the current user.

This use case will observe and return the list of members of a given conversation.

UseCase for observing if User was notified about conversation being subject of legal hold

UseCase for observing if User was notified about verification degrading of conversation

Observes the list of conversation members that are eligible to be promoted to admin role.

This use case will observe and return the list of users objects, contacts and connections. Using a list of user ids to obverse.

Use case for observing current users typing in a given conversation. This will get their info details from the local database.

Recovers the self user's MLS conversations after synchronization is live. Established groups are checked first, then pending groups are joined in a fresh transaction.

Iterate over all MLS Established conversations after 404 sync error and check for out of sync epochs, if out of sync then it tries to re-join.

Refresh conversations without metadata, only if necessary.

Renames a conversation by its ID.

UseCase for sending a typing event to a specific ConversationId

UseCase for setting legal_hold_change_notified flag to true, it means that User was notified about the recent change in legal hold status.

UseCase for setting DegradedConversationNotified flag to true, means user was notified about verification changes and no need to do it again.

Use case to sync the conversation code. This use case is used to update the conversation code in the database.

This use case will sync against the backend the conversations of the current user.

This use case will update the access and access role configuration of a conversation. So we can operate and allow or not operation based on these roles:

This use case will update last read date for a conversation. After that, will sync against other user's registered clients, using the self conversation.

Internal UseCase that updates Group Conversation Receipt Mode value Possible values: Conversation.ReceiptMode.ENABLED and Conversation.ReceiptMode.DISABLED Returns: ConversationUpdateReceiptModeResult

Split the name in tokens. Any character that is not a alphanumeric character is a separator (e.g. (space), -, !, 🤣 and so on)