Get desktop application:
View/edit binary Protocol Buffers messages
Pseudo-entity that indicates the given alias JID is blocked by the requesting user
Used in:
Used in:
,Background Pic Extension
Used in:
, , , ,The details of this profile pic extension
Used in:
, , , ,a biography or short biographical profile of someone or some group
The BotExtensionElement may not be present if this user is not a bot If a user is a bot then BotExtensionElement will be present and is_bot will be true Eventually this element will contain fields such as isTrusted and other attributes
Used in:
Used in:
a short description of a bot, user or a group
Used in:
, ,The id of the chat theme product to be displayed - the chat theme assets are fetched from the product data service
Used in:
,The current permission settings for modifying a conversation's chat theme
Used in:
Used in:
, ,Used in:
, ,Used in:
Use tag number range of [100-199] for elements sourced from profile service
Original Profile Pic Extension
Background Pic Extension
Registration Element for bot
Byline for a bot
Rating information for the bot
Is the bot trusted
Used in:
Used in:
Use tag number range of [100-199] for elements sourced from profile service
Original Profile Pic Extension
Background Pic Extension
Maximum Group Size
Is KIN enabled
Entity containing information of group that is broadcast to its members' rosters.
Used in:
,Hashtag for the group
************************************************** Key used by Entity Warehouse, Subscription Service, etc to explicitly identify entities ************************************************** NOTE: EntityKey has specific IDs that are expected to go with specific EntityTypes. Please check the comments for EntityType to understand what id values are valid (Ideally we would restructure the EntityKey message, but it's already too embedded to change now)
user_jid requires type to be USER or USER_ROSTER_ENTRY
group_jid requires type to be GROUP or GROUP_ROSTER_ENTRY
convo_id requires type to be CONVO
alias_jid requires type to be ALIAS_BLOCK_ENTRY
Used in:
USER - expects id to contain 'user_jid'
GROUP - expects id to contain 'group_jid'
USER_ROSTER_ENTRY - expects id to contain 'user_jid'
GROUP_ROSTER_ENTRY - expects id to contain 'group_jid'
CONVO - expects id to contain 'convo_id'
Note: ALIAS_BLOCK_ENTRY is not an entity type actually stored within EntityWarehouse. Used to identify a pseudo-entity for use within Internal Subscription Service. ALIAS_BLOCK_ENTRY - expects id to contain 'alias_jid'
Used in:
Use tag number range of [100-199] for elements sourced from profile service
Original Profile Pic Extension
Background Pic Extension
Registration Element for user
User Interests Element
Anon Match Avatar Element
Kin User ID Element
Entity containing information of a single user that is broadcasted to his/her rosters.
Used in:
,The presence of this element indicates that this User is a bot, regardless of the element's content; Regular Users will never have this element.
User type of the account
Hashtag for a group
Used in:
Used in:
All the roster info for a single group member that's part of a GroupRosterEntry
Note; To people looking at this in the future, DO NOT be tempted to merge user_jid and alias_jid into a oneof. We can't do it.
Used in:
We added the alias_jid field too late. There are some issues here, and no solution is perfect. Firstly, the database is already populated with user_jid values and those can NEVER change Why is alias_jid of type XiAliasJid though and not XiBareUserJid? Consider how both of these fields work together. If user_jid is not there, check for alias_jid if alias_jid is not there, check for user_jid The three relevant types are XiBareUserJid, XiAliasJid, and XiBareUserOrAliasJid If we remove or change the type of field 1 then we need to convert a bunch of values in the database but changing this API at the time of writing was too high priority to do that and so field 1 must remain an XiBareUserJid Given that field 1 remains unchanged, we still need to somehow work an XiAliasJid into this message Only two options make any sense. We can make field 3 an XiBareUserOrAliasJid or make it an XiAliasJid We went with an XiAliasJid based on some pretty razor thin advantages and disadvantages, but either way would have created an API that is less than ideal. That's why no oneof and no XiBareUserOrAliasJid
Should only be present for public groups that are converted
Used in:
Just a wrapper so we can make it optional
Used in:
Used in:
Contains an kik asset id. A Kik Asset is something that is premade by us and provided to users A kik_asset_id might be something like SMILEY_FACE or FLAG_USA if those assets existed
Used in:
,The id of a Kik Asset
Contains the details of any pic that is accessible by URL
Used in:
Full Sized Pic URL
Thumbnail Sized Pic URL
Used in:
, ,Used in:
Either or not Kin functionality is enabled
Used in:
Used in:
, ,Kin User ID maps a Kik user to their Kin wallet address, and is included in all transaction JWT tokens
The maximum number of members allowed in the group concurrently
Used in:
A zero value is more likely to mean there's a widespread problem with groups in general than that this group's maximum member size is really zero. In either case, program defensively and don't allow users to join a group if its size is zero.
Original Profile Pic Extension
Used in:
, , ,The details of this profile pic extension
Used in:
, , ,Used in:
,A picture element. If the user uploads a picture use this
A Kik Asset element. If the original pic is something we provide, use this
Used in:
Contains the rating details for an entity.
Used in:
Used in:
, ,System time of when the user/group is created or registered
Used in:
OneOf user or group
Only applies to user rosters Has this person being blocked by roster owner?
Used in:
,Clients MUST NOT interpret this message.
Used in:
Used in:
,Used in:
,