package common.messaging.v2

Get desktop application:
View/edit binary Protocol Buffers messages

Chat represents the 'metadata' about a Chat. A chat is fundamentally broken down into: 1. Metadata (id, type info, etc) 2. Message Log (log of actual messages) 3. Pointer States This represents (1), while the other two only have accessors via APIs, since implementations of (2) and (3) are highly varied between server and clients.

Used in: mobile.chats.v2.GetChatInfoStreamResponse, mobile.groups.v2.CreateGroupResponse

• optional v2.ChatId id = 1

• oneof info

  Contains minimal chat info depending on the type of chat. Note that this oneof is required.

  • chats.v2.OneToOneInfo one_to_one_info = 2

  • chats.v2.GroupInfoShort group_info = 3

• optional chats.v2.ChatThemeId chat_theme_id = 4

  Optional chat theme of this chat.

• optional chats.v2.MuteStatus mute_status = 5

  Optional mute status of this chat. Note that this is caller sensitive as it denotes whether or not the _caller_ has muted the chat. Multiple members of a chat might see different mute statuses here.

• optional v2.ChatId chat_id = 1

• oneof preview

  An optional preview of the chat. This is only to be used for rendering purposes on the chat list stream. It must not be used for any chat storage.

  • ChatUpdate.TextPreview text_preview = 2

  • ChatUpdate.ImagePreview image_preview = 3

• optional ChatUpdate.NameUpdate name_update = 4

  NameUpdate indicates that there is an update to the name of the chat.

• optional ChatUpdate.ProfilePicUpdate profile_pic_update = 5

  If ProfilePicUpdate is set, then there is an update to the chat's profile picture.

• optional ChatUpdate.ParticipantsUpdate participants_update = 6

  If ParticipansChange is set, then the participants of the chat has changed, and clients should call out to the respective services to refresh their participants list.

todo: fill me out

Used in: ChatUpdate

(message has no fields)

Used in: ChatUpdate

• string name = 3

  Note: If name is an empty string, then this is indicitive of the name being cleared. It is up to the client to determine what should be rendered.

Used in: ChatUpdate

• repeated v2.PersonaId participant_ids = 1

  todo: deal with diffing? perhaps anything larger than a certain size will not be participants

Used in: ChatUpdate

• string profile_pic_url = 4

Used in: ChatUpdate

• string preview_text = 1

Message represents the a message. For now, it only includes the bare minimum for message routing / MLSM model. A fully defined message model still needs to be defined (initial work was started multiple times).

• optional Message.Id id = 1

  Note: ID will be constructed in such a way that ID(M_n) < ID(M_n+1), where n is the order in the underlying message log (as seen by server). If time was a universal truth, and servers had 100% accuracy, ID(M_n) would be the time that the server inserted it into the log. The ID(M_n) < ID(M_n+1) invariant is the _only_ assumption that can be made about the ID. The comparator is a lexical sort. IDs are _only_ gaurenteed to be unique within a given Chat. Collisions can (and will) occure cross-chats. For example, upgrading a 1:1 -> Group chat results in a log copy, which (intentionally) retains the IDs.

• optional v2.ChatId chat_id = 2

• optional v2.PersonaId sender = 3

• optional google.protobuf.Timestamp client_sent = 4

  Only used for rendering purposes.

• string body = 5

Used in: Message, Pointer

• bytes raw_value = 1

• optional v2.ChatId chat_id = 1

• optional Message.Id message_id = 2

• optional v2.PersonaId persona = 3

• Pointer.Type type = 4

Used in: Pointer

• PUSHED = 0

• DELIVERED = 1

• READ = 2