Allow only participants of certain chats
inputPrivacyValueAllowChatParticipants#840649cf chats:Vector<long> = InputPrivacyRule;| Name | Type | Description |
|---|---|---|
| chats | Vector<long> | Allowed chat IDs (either a chat or a supergroup ID, verbatim the way it is received in the constructor (i.e. unlike with bot API IDs, here group and supergroup IDs should be treated in the same way)). |
Info about a group.
When updating the local peer database, all fields from the newly received constructor take priority over the old constructor cached locally (including by removing fields that aren't set in the new constructor).
See here » for an implementation of the logic to use when updating the local user peer database.
Channel/supergroup info
When updating the local peer database, all fields from the newly received constructor take priority over the old constructor cached locally (including by removing fields that aren't set in the new constructor).
The only exception to the above rule is when the min flag is set, in which case only the following fields must be applied over any locally stored version:
titlemegagroupcolorphotousernameusernameshas_geonoforwardsemoji_statushas_linkslow_mode_enabledscamfakegigagroupforumlevelrestrictedrestriction_reasonjoin_to_sendjoin_requestis_verifieddefault_banned_rightssignature_profilesautotranslationbroadcast_messages_allowedmonoforumforum_tabslinked_monoforum_idsend_paid_messages_starsbot_verification_iconSee here » for an implementation of the logic to use when updating the local user peer database.