diff --git a/data/web/corefork.telegram.org/api/files.html b/data/web/corefork.telegram.org/api/files.html index 001960f8f3..306138a88d 100644 --- a/data/web/corefork.telegram.org/api/files.html +++ b/data/web/corefork.telegram.org/api/files.html @@ -131,7 +131,7 @@ After the entire file is successfully saved, the final method may be called and
Use messages.editMessage to edit or replace a media file sent using messages.sendMedia and messages.sendMultiMedia.
If one wishes to edit only the spoiler
, ttl_seconds
or query
attributes of the media, this may be done without reuploading the entire media file, by simply passing the old media to the id
parameter of inputMediaPhoto, inputMediaDocument and updating the values of the spoiler
/ttl_seconds
/query
attributes as needed.
If one wishes to edit any other attribute (for example, the file name specified in documentAttributeFilename, any other DocumentAttribute or any flag different from spoiler
/ttl_seconds
/query
) a full reupload of the file is required, in order to be able to specify the new attributes in inputMediaUploadedPhoto/inputMediaUploadedDocument.
The only exception to this rule is when editing the documentAttributeVideo.video_start_ts
attribute of video stories, in which case inputMediaDocument may still be used with inputFileStoryDocument instead of inputFile without reuploading the entire story video, see here » for more info on the full flow.
The only exception to this rule is when editing the documentAttributeVideo.video_start_ts
attribute of video stories, in which case inputMediaDocument may still be used with inputFileStoryDocument instead of inputFile without reuploading the entire story video, see here » for more info on the full flow.
The API also supports streamed uploads, in cases where the length of the file is not known before starting the upload.
This is useful for example when converting a video, to avoid buffering the entire converted video on the filesystem, each part is uploaded immediately as soon as it is produced by the encoder.
diff --git a/data/web/corefork.telegram.org/api/stories.html b/data/web/corefork.telegram.org/api/stories.html index d0ba36230d..8975fdd50d 100644 --- a/data/web/corefork.telegram.org/api/stories.html +++ b/data/web/corefork.telegram.org/api/stories.html @@ -86,7 +86,7 @@ Note that if any of the conditions changes in the period between the call to The parameters of stories.sendStory are fully described on the method page », here are some of the most important ones:peer
: The peer to send the story as.media
: The story media.media
: The story media (a vertical photo or a vertical video, max 30 MB).media_areas
: Media areas associated to the story, see here » for more info.privacy_rules
: A set of privacy rules » for the story as an array of InputPrivacyRule constructors, indicating who can or can't view the story.expire
: Period after which the story is moved to archive (and to the profile if pinned
is set), in seconds; must be one of 6 * 3600
, 12 * 3600
, 86400
, or 2 * 86400
for Telegram Premium users, and 86400
otherwise.