From 02f596abcaeef50193480ecbcf2fe1450428c92a Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Wed, 24 Jul 2024 18:02:48 +0000 Subject: [PATCH] Update content of files --- data/web/corefork.telegram.org/api/privacy.html | 2 +- .../inputPrivacyKeyStatusTimestamp.html | 3 ++- .../constructor/privacyKeyStatusTimestamp.html | 15 +++++++++++---- .../corefork.telegram.org/constructor/user.html | 6 +++--- .../constructor/userStatusLastMonth.html | 11 +++++++++-- .../constructor/userStatusLastWeek.html | 11 +++++++++-- .../constructor/userStatusRecently.html | 11 +++++++++-- .../users.getIsPremiumRequiredToContact.html | 2 +- 8 files changed, 45 insertions(+), 16 deletions(-) diff --git a/data/web/corefork.telegram.org/api/privacy.html b/data/web/corefork.telegram.org/api/privacy.html index f47c464548..b7f1eaa765 100644 --- a/data/web/corefork.telegram.org/api/privacy.html +++ b/data/web/corefork.telegram.org/api/privacy.html @@ -114,7 +114,7 @@ account.setPrivacy#c9f81ce8 key:InputPrivacyKey rules:Vector<InputPrivacyRule> = account.PrivacyRules;

Privacy keys together with privacy rules » indicate what can or can't someone do and are specified by a PrivacyKey constructor, and its input counterpart InputPrivacyKey.
InputPrivacyKey constructors are passed as input to methods that accept privacy keys, while PrivacyKeys are contained in constructors returned by the API.

-

See the type page » for a full list of privacy keys and their descriptions.

+

See the type page » for a full list of privacy keys and their descriptions.

Use account.getPrivacy to obtain the current set of rules associated to a key, and account.setPrivacy to change it.

Changing the privacy settings will trigger an updatePrivacy, sent to all currently logged in sessions of the current account.

Global privacy settings

diff --git a/data/web/corefork.telegram.org/constructor/inputPrivacyKeyStatusTimestamp.html b/data/web/corefork.telegram.org/constructor/inputPrivacyKeyStatusTimestamp.html index 913608c07a..bd0d3763f8 100644 --- a/data/web/corefork.telegram.org/constructor/inputPrivacyKeyStatusTimestamp.html +++ b/data/web/corefork.telegram.org/constructor/inputPrivacyKeyStatusTimestamp.html @@ -43,7 +43,8 @@

inputPrivacyKeyStatusTimestamp

Whether people will be able to see our exact last online timestamp.

-

Note that if we decide to hide our exact last online timestamp to someone and we do not have a Premium subscription, we won't be able to see the exact last online timestamp of any user, including those that do share it with us.

+

Note that if we decide to hide our exact last online timestamp to someone (i.e., users A, B, C, or all users) and we do not have a Premium subscription, we won't be able to see the exact last online timestamp of those users (A, B, C, or all users), even if those users do share it with us.

+

If those users do share their exact online status with us, but we can't see it due to the reason mentioned above, the by_me flag of userStatusRecently, userStatusLastWeek, userStatusLastMonth will be set.

  • diff --git a/data/web/corefork.telegram.org/constructor/privacyKeyStatusTimestamp.html b/data/web/corefork.telegram.org/constructor/privacyKeyStatusTimestamp.html index e4c4bcaba2..b320452172 100644 --- a/data/web/corefork.telegram.org/constructor/privacyKeyStatusTimestamp.html +++ b/data/web/corefork.telegram.org/constructor/privacyKeyStatusTimestamp.html @@ -4,10 +4,10 @@ privacyKeyStatusTimestamp - + - + @@ -43,7 +43,8 @@

    privacyKeyStatusTimestamp

    Whether we can see the last online timestamp of this user.

    -

    Note that if we decide to hide our exact last online timestamp to someone and we do not have a Premium subscription, we won't be able to see the exact last online timestamp of any user, including those that do share it with us.

    +

    Note that if we decide to hide our exact last online timestamp to someone (i.e., users A, B, C, or all users) and we do not have a Premium subscription, we won't be able to see the exact last online timestamp of those users (A, B, C, or all users), even if those users do share it with us.

    +

    If those users do share their exact online status with us, but we can't see it due to the reason mentioned above, the by_me flag of userStatusRecently, userStatusLastWeek, userStatusLastMonth will be set.

    • @@ -63,7 +64,13 @@

      PrivacyKey

      Related pages

      Telegram Premium

      -

      Telegram Premium is an optional subscription service that unlocks additional exclusive client-side and API-side features, while helping support the development of the app.

    +

    Telegram Premium is an optional subscription service that unlocks additional exclusive client-side and API-side features, while helping support the development of the app.

    +

    userStatusRecently

    +

    Online status: last seen recently

    +

    userStatusLastWeek

    +

    Online status: last seen last week

    +

    userStatusLastMonth

    +

    Online status: last seen last month

diff --git a/data/web/corefork.telegram.org/constructor/user.html b/data/web/corefork.telegram.org/constructor/user.html index 2b11b7e7ae..f7f8730bb2 100644 --- a/data/web/corefork.telegram.org/constructor/user.html +++ b/data/web/corefork.telegram.org/constructor/user.html @@ -141,7 +141,7 @@ apply_min_photo flags.25?true -If set and min is set, the value of photo can be used to update the local database, see the documentation of that flag for more info. +If set and min is set, the value of photo can be used to update the local database, see the documentation of that flag for more info. fake @@ -156,7 +156,7 @@ premium flags.28?true -Whether this user is a Telegram Premium user
Changes to this flag should invalidate the local userFull cache for this user ID.
Changes to this flag if the self flag is set should also trigger the following calls, to refresh the respective caches:
- help.getConfig
- messages.getTopReactions if the bot flag is not set +Whether this user is a Telegram Premium user
Changes to this flag should invalidate the local userFull cache for this user ID.
Changes to this flag if the self flag is set should also trigger the following calls, to refresh the respective caches:
- help.getConfig
- messages.getTopReactions if the bot flag is not set attach_menu_enabled @@ -206,7 +206,7 @@ access_hash flags.0?long -Access hash of the user, see here » for more info.
If this flag is set, when updating the local peer database, generate a virtual flag called min_access_hash, which is:
- Set to true if min is set AND
- The phone flag is not set OR
- The phone flag is set and the associated phone number string is non-empty
- Set to false otherwise.

Then, apply both access_hash and min_access_hash to the local database if:
- min_access_hash is false OR
- min_access_hash is true AND
- There is no locally cached object for this user OR
- There is no access_hash in the local cache OR
- The cached object's min_access_hash is also true
If the final merged object stored to the database has the min_access_hash field set to true, the related access_hash is only suitable to use in inputPeerPhotoFileLocation », to directly download the profile pictures of users, everywhere else a inputPeer*FromMessage constructor will have to be generated as specified here ».
Bots can also use min access hashes in some conditions, by passing 0 instead of the min access hash. +Access hash of the user, see here » for more info.
If this flag is set, when updating the local peer database, generate a virtual flag called min_access_hash, which is:
- Set to true if min is set AND
- The phone flag is not set OR
- The phone flag is set and the associated phone number string is non-empty
- Set to false otherwise.

Then, apply both access_hash and min_access_hash to the local database if:
- min_access_hash is false OR
- min_access_hash is true AND
- There is no locally cached object for this user OR
- There is no access_hash in the local cache OR
- The cached object's min_access_hash is also true
If the final merged object stored to the database has the min_access_hash field set to true, the related access_hash is only suitable to use in inputPeerPhotoFileLocation », to directly download the profile pictures of users, everywhere else a inputPeer*FromMessage constructor will have to be generated as specified here ».
Bots can also use min access hashes in some conditions, by passing 0 instead of the min access hash. first_name diff --git a/data/web/corefork.telegram.org/constructor/userStatusLastMonth.html b/data/web/corefork.telegram.org/constructor/userStatusLastMonth.html index 90e61cd1cd..c2c93686bb 100644 --- a/data/web/corefork.telegram.org/constructor/userStatusLastMonth.html +++ b/data/web/corefork.telegram.org/constructor/userStatusLastMonth.html @@ -74,12 +74,19 @@ by_me flags.0?true -  +If set, the exact user status of this user is actually available to us, but to view it we must first purchase a Premium subscription, or allow this user to see our exact last online status. See here » for more info.

Type

-

UserStatus

+

UserStatus

+

Related pages

+

Telegram Premium

+

Telegram Premium is an optional subscription service that unlocks additional exclusive client-side and API-side features, while helping support the development of the app.

+

privacyKeyStatusTimestamp

+

Whether we can see the last online timestamp of this user.

+

Note that if we decide to hide our exact last online timestamp to someone (i.e., users A, B, C, or all users) and we do not have a Premium subscription, we won't be able to see the exact last online timestamp of those users (A, B, C, or all users), even if those users do share it with us.

+

If those users do share their exact online status with us, but we can't see it due to the reason mentioned above, the by_me flag of userStatusRecently, userStatusLastWeek, userStatusLastMonth.

diff --git a/data/web/corefork.telegram.org/constructor/userStatusLastWeek.html b/data/web/corefork.telegram.org/constructor/userStatusLastWeek.html index 3140c04707..252dc2dcb2 100644 --- a/data/web/corefork.telegram.org/constructor/userStatusLastWeek.html +++ b/data/web/corefork.telegram.org/constructor/userStatusLastWeek.html @@ -74,12 +74,19 @@ by_me flags.0?true -  +If set, the exact user status of this user is actually available to us, but to view it we must first purchase a Premium subscription, or allow this user to see our exact last online status. See here » for more info.

Type

-

UserStatus

+

UserStatus

+

Related pages

+

Telegram Premium

+

Telegram Premium is an optional subscription service that unlocks additional exclusive client-side and API-side features, while helping support the development of the app.

+

privacyKeyStatusTimestamp

+

Whether we can see the last online timestamp of this user.

+

Note that if we decide to hide our exact last online timestamp to someone (i.e., users A, B, C, or all users) and we do not have a Premium subscription, we won't be able to see the exact last online timestamp of those users (A, B, C, or all users), even if those users do share it with us.

+

If those users do share their exact online status with us, but we can't see it due to the reason mentioned above, the by_me flag of userStatusRecently, userStatusLastWeek, userStatusLastMonth.

diff --git a/data/web/corefork.telegram.org/constructor/userStatusRecently.html b/data/web/corefork.telegram.org/constructor/userStatusRecently.html index 73248abd8a..3f95126ed6 100644 --- a/data/web/corefork.telegram.org/constructor/userStatusRecently.html +++ b/data/web/corefork.telegram.org/constructor/userStatusRecently.html @@ -74,12 +74,19 @@ by_me flags.0?true -  +If set, the exact user status of this user is actually available to us, but to view it we must first purchase a Premium subscription, or allow this user to see our exact last online status. See here » for more info.

Type

-

UserStatus

+

UserStatus

+

Related pages

+

Telegram Premium

+

Telegram Premium is an optional subscription service that unlocks additional exclusive client-side and API-side features, while helping support the development of the app.

+

privacyKeyStatusTimestamp

+

Whether we can see the last online timestamp of this user.

+

Note that if we decide to hide our exact last online timestamp to someone (i.e., users A, B, C, or all users) and we do not have a Premium subscription, we won't be able to see the exact last online timestamp of those users (A, B, C, or all users), even if those users do share it with us.

+

If those users do share their exact online status with us, but we can't see it due to the reason mentioned above, the by_me flag of userStatusRecently, userStatusLastWeek, userStatusLastMonth.

diff --git a/data/web/corefork.telegram.org/method/users.getIsPremiumRequiredToContact.html b/data/web/corefork.telegram.org/method/users.getIsPremiumRequiredToContact.html index 379ac0936a..bf66672f51 100644 --- a/data/web/corefork.telegram.org/method/users.getIsPremiumRequiredToContact.html +++ b/data/web/corefork.telegram.org/method/users.getIsPremiumRequiredToContact.html @@ -42,7 +42,7 @@

users.getIsPremiumRequiredToContact

-

Check whether we can write to the specified user (non-Premium users only), see here » for more info on the full flow.

+

Check whether we can write to the specified user (this method can only be called by non-Premium users), see here » for more info on the full flow.