Use contacts.getStatuses to obtain the online statuses of all contacts with a phone number.
+Use contacts.getStatuses to obtain the online statuses of all contacts with an accessible associated Telegram account.
Schema:
contacts.found#b3134d9d my_results:Vector<Peer> results:Vector<Peer> chats:Vector<Chat> users:Vector<User> = contacts.Found;
@@ -156,7 +156,7 @@ Note that according to the user's privacy settings, n
contacts.resetSaved#879537f1 = Bool;Use contacts.deleteContacts to delete contacts with an associated Telegram account; the returned Updates will contain updated user information.
Use contacts.deleteByPhones to delete contacts by their phone number, even if they don't have an associated Telegram account.
-Use contacts.resetSaved to remove all contacts (both those with and without an associated Telegram account).
+Use contacts.resetSaved to remove all contacts (both those without an associated Telegram account).
diff --git a/data/web/corefork.telegram.org/api/layers.html b/data/web/corefork.telegram.org/api/layers.html index 2e9bb0d8f7..f80651f94b 100644 --- a/data/web/corefork.telegram.org/api/layers.html +++ b/data/web/corefork.telegram.org/api/layers.html @@ -62,6 +62,7 @@Also added documentation for streamed uploads and improved the method queue documentation.
+The RPC error database » was also updated.
The following new deep links were added:
Introducing privacy settings for user bios, improved login code invalidation, improved chat invites, improved update handling, sponsored websites and click reporting for sponsored messages.
-Also, anonymous channel admins can now vote in polls.
+Also, anonymous channels can now vote in polls: when invoking messages.sendVote, the vote will be sent from the peer specified using messages.saveDefaultSendAs.
It is recommended to use limit 10-100 for channels and 1000-10000 otherwise.
Clients may ask the API to passively send them updates for channels/supergroups they haven't joined, by simply making a updates.getChannelDifference query.
-If the specified channel or supergroup is public, or is private but temporarily available for a limited time thanks to a chatInvitePeek, the API will start passively sending updates (i.e. as standalone Updates constructors in the socket, as is already the case for normal channels/supergroups we've already joined), as long as the client continues to periodically invoke updates.getChannelDifference every timeout seconds (returned by the method, or every 10 seconds if the timeout flag is absent from the return value of the method).
To stop passively receiving updates, simply stop invoking updates.getChannelDifference, and the API will automatically stop passively sending updates after a while.
+If the specified channel or supergroup is public, or is private but temporarily available for a limited time thanks to a chatInvitePeek, the API will start passively sending updates (i.e. as standalone Updates constructors in the socket, as is already the case for normal channels/supergroups we've already joined) to all logged-in sessions, as long as any of the sessions continues to periodically invoke updates.getChannelDifference every timeout seconds (returned by the method, or every 10 seconds if the timeout flag is absent from the return value of the method).
To stop passively receiving updates, simply stop invoking updates.getChannelDifference, and the API will automatically stop passively sending updates after a while.
Implementations also have to take care to postpone updates received via the socket while filling gaps in the event and Update sequences, as well as avoid filling gaps in the same sequence.
Example implementations: tdlib, MadelineProto.
diff --git a/data/web/corefork.telegram.org/constructor/messagePeerReaction.html b/data/web/corefork.telegram.org/constructor/messagePeerReaction.html index 8da76aedf2..0e807c2000 100644 --- a/data/web/corefork.telegram.org/constructor/messagePeerReaction.html +++ b/data/web/corefork.telegram.org/constructor/messagePeerReaction.html @@ -112,7 +112,7 @@React to message.
Starting from layer 159, the reaction will be sent from the peer specified using messages.saveDefaultSendAs.
Change the default peer that should be used when sending messages to a specific group
+Change the default peer that should be used when sending messages, reactions, poll votes to a specific group
diff --git a/data/web/corefork.telegram.org/constructor/poll.html b/data/web/corefork.telegram.org/constructor/poll.html index 381e9575b4..c9826f2390 100644 --- a/data/web/corefork.telegram.org/constructor/poll.html +++ b/data/web/corefork.telegram.org/constructor/poll.html @@ -122,7 +122,8 @@Vote in a poll
+Vote in a poll
+Starting from layer 159, the vote will be sent from the peer specified using messages.saveDefaultSendAs.
diff --git a/data/web/corefork.telegram.org/constructor/pollAnswer.html b/data/web/corefork.telegram.org/constructor/pollAnswer.html index 574b100ce8..63a709bf85 100644 --- a/data/web/corefork.telegram.org/constructor/pollAnswer.html +++ b/data/web/corefork.telegram.org/constructor/pollAnswer.html @@ -82,7 +82,8 @@Vote in a poll
+Vote in a poll
+Starting from layer 159, the vote will be sent from the peer specified using messages.saveDefaultSendAs.
diff --git a/data/web/corefork.telegram.org/constructor/pollAnswerVoters.html b/data/web/corefork.telegram.org/constructor/pollAnswerVoters.html index 63e2e41d0a..524e509c75 100644 --- a/data/web/corefork.telegram.org/constructor/pollAnswerVoters.html +++ b/data/web/corefork.telegram.org/constructor/pollAnswerVoters.html @@ -97,7 +97,8 @@Vote in a poll
+Vote in a poll
+Starting from layer 159, the vote will be sent from the peer specified using messages.saveDefaultSendAs.
diff --git a/data/web/corefork.telegram.org/method/contacts.getContactIDs.html b/data/web/corefork.telegram.org/method/contacts.getContactIDs.html index 5ea81d50fa..026afddda5 100644 --- a/data/web/corefork.telegram.org/method/contacts.getContactIDs.html +++ b/data/web/corefork.telegram.org/method/contacts.getContactIDs.html @@ -4,10 +4,10 @@Get the telegram IDs of all contacts.
-Returns an array of Telegram user IDs for all contacts (0 if a contact does not have an associated Telegram account or have hidden their account using privacy settings).
Returns the list of contact statuses.
+Use this method to obtain the online statuses of all contacts with an accessible associated Telegram account.
Change the default peer that should be used when sending messages to a specific group
+Change the default peer that should be used when sending messages, reactions, poll votes to a specific group
Telegram allows users to react on any message using specific emojis, triggering cute lottie animations.
Change the default peer that should be used when sending messages to a specific group
+Change the default peer that should be used when sending messages, reactions, poll votes to a specific group
The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.
Vote in a poll
+Starting from layer 159, the vote will be sent from the peer specified using messages.saveDefaultSendAs.
Poll
Poll
+Change the default peer that should be used when sending messages, reactions, poll votes to a specific group