To set up two-factor authorization on an already authorized account, follow the SRP 2FA authentication docs.
Each phone number is limited to only a certain amount of logins per day (e.g. 5, but this is subject to change) after which the API will return a FLOOD error until the next day. This might not be enough for testing the implementation of User Authorization flows in client applications.
-There are several reserved phone number prefixes for testing that your application handles redirects between DCs, sign up, sign in and 2FA flows correctly. These numbers are only available on Test DCs (their IP addresses for TCP transport are availble in API development tools panel after api_id was obtained, URI format for HTTPS/Websocket transport).
+There are several reserved phone number prefixes for testing that your application handles redirects between DCs, sign up, sign in and 2FA flows correctly. These numbers are only available on Test DCs (their IP addresses for TCP transport are available in API development tools panel after api_id was obtained, URI format for HTTPS/Websocket transport).
If you wish to emulate an application of a user associated with DC number X, it is sufficient to specify the phone number as 99966XYYYY, where YYYY are random numbers, when registering the user. A user like this would always get XXXXX as the login confirmation code (the DC number, repeated five times). Note that the value of X must be in the range of 1-3 because there are only 3 Test DCs. When the flood limit is reached for any particular test number, just choose another number (changing the YYYY random part).
Do not store any important or private information in the messages of such test accounts; anyone can make use of the simplified authorization mechanism – and we periodically wipe all information stored there.
Proceed with User Authorization flows in Production DCs only after you make sure everything works correctly on Test DCs first to avoid reaching flood limits.
diff --git a/data/corefork.telegram.org/api/bots/buttons.html b/data/corefork.telegram.org/api/bots/buttons.html index 04e277f869..7d7057a42d 100644 --- a/data/corefork.telegram.org/api/bots/buttons.html +++ b/data/corefork.telegram.org/api/bots/buttons.html @@ -132,7 +132,7 @@ The same should happen when clicking on messages.botCallbackAnswer constructor contains:message if specified, a message that should be shown in a non-blocking toast notificationalert indicates whether the message should be shown as a dismissable prompt, instead of a simple toast notificationalert indicates whether the message should be shown as a dismissible prompt, instead of a simple toast notificationhas_url Whether an URL is presenturl if specified, the client should open the URL, without showing a confirmation prompt. t.me/bot?start=aaa)For old deprecated photos, if the client has cached some old fileLocations with the deprecated secret identifier, inputFileLocation or inputPhotoLegacyFileLocation is used (this is mainly used for backwards compatiblity with bot API file IDs, all user clients must use the modern inputPhotoFileLocation file IDs):
For old deprecated photos, if the client has cached some old fileLocations with the deprecated secret identifier, inputFileLocation or inputPhotoLegacyFileLocation is used (this is mainly used for backwards compatibility with bot API file IDs, all user clients must use the modern inputPhotoFileLocation file IDs):
file_reference, access_hash and id, which are taken from the photo constructor (the last two fields are used only if available, in which case inputPhotoLegacyFileLocation is used instead of inputFileLocation).To send a live geolocation, use messages.sendMedia with an inputMediaGeoLive media .
The inputMediaGeoLive allows sending the geolocation as an inputGeoPoint with floating point latitude and longitude, with an optional accuracy_radius in meters.
Clients can also provide a heading, a direction in degrees (1-360) that can be used to indicate the direction of the user, a validity period for the current location, and a proximity_notification_radius .
The sent geolocation should be updated perioducally using messages.editMessage at most every period seconds, in order to implement the "live" part of live geolocations.
The sent geolocation should be updated periodically using messages.editMessage at most every period seconds, in order to implement the "live" part of live geolocations.
To stop sharing the location, pass inputGeoPointEmpty as location and set the stopped flag to true in a last messages.editMessage call.
geoPoint#b2a2f663 flags:# long:double lat:double access_hash:long accuracy_radius:flags.0?int = GeoPoint;
diff --git a/data/corefork.telegram.org/api/updates.html b/data/corefork.telegram.org/api/updates.html
index 39b73a2321..2c00088d0b 100644
--- a/data/corefork.telegram.org/api/updates.html
+++ b/data/corefork.telegram.org/api/updates.html
@@ -139,7 +139,7 @@ Manually obtaining updates is also required in the following situations:
To fetch the updates difference of a channel, updates.getChannelDifference is used.
If the difference is too large to be received in one request, the final flag of the result is not set (see docs).
The intermediate status, represented by the pts, must be saved on the client and the query must be repeated, using the intermediate status as the current status.
-For perfomance reasons and for better user experience, client can set maximum gap size to be filled: pts_total_limit parameter of updates.getDifference and limit parameter for updates.getChannelDifference can be used.
+For performance reasons and for better user experience, client can set maximum gap size to be filled: pts_total_limit parameter of updates.getDifference and limit parameter for updates.getChannelDifference can be used.
If the gap is too large and there are too many updates to fetch, a *TooLong constructor will be returned. In this case, the client must re-fetch the state, re-start fetching updates from that state and follow the instructions that can be found here.
It is recommended to use limit 10-100 for channels and 1000-10000 otherwise.
Example implementations
diff --git a/data/corefork.telegram.org/constructor/chatAdminRights.html b/data/corefork.telegram.org/constructor/chatAdminRights.html
index c0ce01ae7d..8fc9878f0e 100644
--- a/data/corefork.telegram.org/constructor/chatAdminRights.html
+++ b/data/corefork.telegram.org/constructor/chatAdminRights.html
@@ -121,7 +121,7 @@
other
flags.12?true
-Set this flag if none of the other flags are set, but you stil want the user to be an admin.
+Set this flag if none of the other flags are set, but you still want the user to be an admin.
diff --git a/data/corefork.telegram.org/constructor/document.html b/data/corefork.telegram.org/constructor/document.html
index a9b825ede8..1c76dcf122 100644
--- a/data/corefork.telegram.org/constructor/document.html
+++ b/data/corefork.telegram.org/constructor/document.html
@@ -76,7 +76,7 @@
access_hash
long
-Check sum, dependant on document ID
+Check sum, dependent on document ID
file_reference
diff --git a/data/corefork.telegram.org/constructor/encryptedChat.html b/data/corefork.telegram.org/constructor/encryptedChat.html
index 5ca4532384..ffac63fdf5 100644
--- a/data/corefork.telegram.org/constructor/encryptedChat.html
+++ b/data/corefork.telegram.org/constructor/encryptedChat.html
@@ -71,7 +71,7 @@
access_hash
long
-Check sum dependant on the user ID
+Check sum dependent on the user ID
date
diff --git a/data/corefork.telegram.org/constructor/inputEncryptedFileUploaded.html b/data/corefork.telegram.org/constructor/inputEncryptedFileUploaded.html
index 7a3b72e976..0dd6d70182 100644
--- a/data/corefork.telegram.org/constructor/inputEncryptedFileUploaded.html
+++ b/data/corefork.telegram.org/constructor/inputEncryptedFileUploaded.html
@@ -66,7 +66,7 @@
id
long
-Random file ID created by clien
+Random file ID created by client
parts
diff --git a/data/corefork.telegram.org/constructor/messages.statedMessagesLinks b/data/corefork.telegram.org/constructor/messages.statedMessagesLinks
index fea9f00abc..0a32cf747a 100644
--- a/data/corefork.telegram.org/constructor/messages.statedMessagesLinks
+++ b/data/corefork.telegram.org/constructor/messages.statedMessagesLinks
@@ -76,7 +76,7 @@
users
Vector<User>
-List of users mentioned in messages and cahts
+List of users mentioned in messages and chats
links
diff --git a/data/corefork.telegram.org/constructor/pageBlockAuthorDate.html b/data/corefork.telegram.org/constructor/pageBlockAuthorDate.html
index 3d5f3d08d1..83272b4f47 100644
--- a/data/corefork.telegram.org/constructor/pageBlockAuthorDate.html
+++ b/data/corefork.telegram.org/constructor/pageBlockAuthorDate.html
@@ -71,7 +71,7 @@
published_date
int
-Date of pubblication
+Date of publication
diff --git a/data/corefork.telegram.org/constructor/pageRelatedArticle.html b/data/corefork.telegram.org/constructor/pageRelatedArticle.html
index b3bb3c965c..16d7e45494 100644
--- a/data/corefork.telegram.org/constructor/pageRelatedArticle.html
+++ b/data/corefork.telegram.org/constructor/pageRelatedArticle.html
@@ -101,7 +101,7 @@
published_date
flags.4?int
-Date of pubblication
+Date of publication
diff --git a/data/corefork.telegram.org/constructor/pageTableCell.html b/data/corefork.telegram.org/constructor/pageTableCell.html
index a2bf2199c1..8bf359be90 100644
--- a/data/corefork.telegram.org/constructor/pageTableCell.html
+++ b/data/corefork.telegram.org/constructor/pageTableCell.html
@@ -91,7 +91,7 @@
valign_bottom
flags.6?true
-Block vertically-alligned to the bottom
+Block vertically-aligned to the bottom
text
diff --git a/data/corefork.telegram.org/constructor/updateMessageID.html b/data/corefork.telegram.org/constructor/updateMessageID.html
index 190ee0ef51..b04f72fe9a 100644
--- a/data/corefork.telegram.org/constructor/updateMessageID.html
+++ b/data/corefork.telegram.org/constructor/updateMessageID.html
@@ -71,7 +71,7 @@
random_id
long
-Previuosly transferred client random_id identifier
+Previously transferred client random_id identifier
diff --git a/data/corefork.telegram.org/constructor/updates.differenceSlice b/data/corefork.telegram.org/constructor/updates.differenceSlice
index 153b8761f6..ccfda7d501 100644
--- a/data/corefork.telegram.org/constructor/updates.differenceSlice
+++ b/data/corefork.telegram.org/constructor/updates.differenceSlice
@@ -66,7 +66,7 @@
new_messages
Vector<Message>
-List of new messgaes
+List of new messages
new_encrypted_messages
diff --git a/data/corefork.telegram.org/constructor/updates.state b/data/corefork.telegram.org/constructor/updates.state
index 2aa7d77521..4dbf43d9ab 100644
--- a/data/corefork.telegram.org/constructor/updates.state
+++ b/data/corefork.telegram.org/constructor/updates.state
@@ -71,7 +71,7 @@
qts
int
-Position in a sequence of updates in secret chats. For further detailes refer to article secret chats
Parameter was added in eigth layer.
+Position in a sequence of updates in secret chats. For further detailes refer to article secret chats
date
diff --git a/data/corefork.telegram.org/method/phone.toggleGroupCallSettings b/data/corefork.telegram.org/method/phone.toggleGroupCallSettings
index 06806fc3e3..8ce4f37c60 100644
--- a/data/corefork.telegram.org/method/phone.toggleGroupCallSettings
+++ b/data/corefork.telegram.org/method/phone.toggleGroupCallSettings
@@ -89,7 +89,7 @@
join_muted
flags.0?Bool
-Whether all users will bthat join this group calle muted by default upon joining the group call
+Whether all users will that join this group call are muted by default upon joining the group call