Allow all participants of certain chats
privacyValueAllowChatParticipants#6b134e8e chats:Vector<long> = PrivacyRule;
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:
title
megagroup
color
photo
username
usernames
has_geo
noforwards
emoji_status
has_link
slow_mode_enabled
scam
fake
gigagroup
forum
level
restricted
restriction_reason
join_to_send
join_request
is_verified
default_banned_rights
signature_profiles
See here » for an implementation of the logic to use when updating the local user peer database.