package mobile.config.v1

Get desktop application:
View/edit binary Protocol Buffers messages

FeatureConfig is a service that provides global configuration settings for various 'features' at Kik. The term 'feature' here is somewhat loose, but generally refers to some setting that is visible to both mobile and server systems. It is _not_ intended for usages such as AB Tests. AB Tests should be done via the ABTesting service, or through server side implementations. AB Tests _may_ override / ignore settings described by the FeatureConfig service. The FeatureConfig service _may_ return different values based on the caller. Changes to settings are expected to resolve roughly within 24 hours. That is, changes to settings are not expected to be universally visible in real time, as is the case with many back end systems.

• rpc GetFeatureConfigs (GetFeatureConfigsRequest, GetFeatureConfigsResponse)

  feature_config_service.proto:28

  GetFeatureConfigs returns the entire set of feature configurations that _may_ be tailored based on the caller.

  message GetFeatureConfigsRequest

  feature_config_service.proto:45

  GetFeatureConfigRequest is an empty request, that may contain fields in the future. The service _may_ use caller information provided by the Xiphias Bridge via headers.

  (message has no fields)

  message GetFeatureConfigsResponse

  feature_config_service.proto:50

  GetFeatureConfigResponse contains a set of configurations that _may_ be tailored to the caller.

  • uint32 max_group_size = 10

    The default maximum size for both public and private groups.

  • bool user_roster_entry_updates_legacy_roster_timestamp = 11

    Switch for ProfileService updating a user's legacy roster last updated timestamp and legacy profile pic timestamp when that user's UserRosterEntry entity is updated. When this switch is true, the client should retrieve a user's UserRosterEntry entity whenever that user's profile pic timestamp is updated in their legacy roster info.

  • bool entity_service_get_trusted_bots_enabled = 12

    The following boolean are using by the client and server. It controls (enable/disables) the call to EntityService.GetTrustedBots which we know will be obsolete after Harmony 3 is in place and is_trusted is supported properly via harmony roster subscription sync

  • optional google.protobuf.Duration min_duration_between_pull_entity_service_get_trusted_bots = 13

    When the entity_service_get_trusted_bots_enabled is enabled, this is the duration to lapse before the client should invoke another call to EntityService.getTrustedBots

  • uint32 max_user_interests = 14

    The max number of interests an user can select

  • repeated UserInterestListItem current_user_interest_list = 15

    The following is the current list of user interests that will be offered to the user for selection. Verbiage returned is localized using the connecting device locale. Before locale is fully supported, English is returned.

  • repeated ChatInterestListItem current_chat_interest_list = 16

    The list of chat interests Verbiage is what mobile client will display to the user When user picks the interests to chat about, the interest ids are attached to findPartner API.

• rpc GetAllUserInterestIds (GetAllUserInterestIdsRequest, GetAllUserInterestIdsResponse)

  feature_config_service.proto:32

  GetAllUserInterestList returns a list of user interests current or ever existed This is likely only to be used internally for validating if an id is valid.

  message GetAllUserInterestIdsRequest

  feature_config_service.proto:120

  GetAllUserInterestIdsRequest is empty for now, but might include fields in the future

  (message has no fields)

  message GetAllUserInterestIdsResponse

  feature_config_service.proto:128

  This list includes the current interests that an user can pick if he is to update this profile This also include all the interests we ever had offered to the client Don't see the need to return page tokens, when do will add it to the request object and will return the page token here

  • repeated string ids = 1

• rpc GetAllChatInterests (GetAllChatInterestsRequest, GetAllChatInterestsResponse)

  feature_config_service.proto:36

  Returns all chat interests that user can pick and/or chat with. This call is used internally for validating if the id is valid

  message GetAllChatInterestsRequest

  feature_config_service.proto:136

  (message has no fields)

  message GetAllChatInterestsResponse

  feature_config_service.proto:141

  This list includes all the currently pickable and interests picked for all Users in the waiting queue.

  • repeated ChatInterestListItem chat_interests = 1

Used in: GetAllChatInterestsResponse, GetFeatureConfigsResponse

• string id = 1

• string localized_interest = 2

• string localized_ice_breaker = 3

  Optional and only returned when used internally via GetAllChatInterests rpc

Used in: GetFeatureConfigsResponse

• string id = 1

• string localized_verbiage = 2