documentation

TelegramPlayGround · Mar 25, 2024 · 9e54bdf · 9e54bdf
1 parent 0d784e8
commit 9e54bdf
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 6 deletions.
diff --git a/docs/source/releases/changes-in-this-fork.rst b/docs/source/releases/changes-in-this-fork.rst
@@ -12,10 +12,15 @@ it can take advantage of new goodies!
 | Scheme layer used: 176 |
 +------------------------+
 
-- Add ``schedule_date`` parameter to :meth:`~pyrogram.Client.edit_message_caption`, :meth:`~pyrogram.Client.edit_message_media`, :meth:`~pyrogram.Client.edit_message_text`.
+- Bug fix for :meth:`~pyrogram.Client.send_message` with the ``message_thread_id`` parameter.
+- Added ``request_users`` and ``request_chat`` to :obj:`~pyrogram.types.KeyboardButton`.
+- Added :obj:`~pyrogram.types.Giveaway`, ``users_shared``, ``chat_shared`` to :obj:`~pyrogram.types.Message`.
+- **NOTE**: using the ``scheduled`` parameter, please be aware about using the correct :doc:`Message Identifiers <../../topics/message-identifiers>`.
+    - Add ``is_scheduled`` parameter to :meth:`~pyrogram.Client.delete_messages`.
+    - Add ``schedule_date`` parameter to :meth:`~pyrogram.Client.edit_message_caption`, :meth:`~pyrogram.Client.edit_message_media`, :meth:`~pyrogram.Client.edit_message_text`.
+    - Added ``is_scheduled`` to :meth:`~pyrogram.Client.get_messages`.
+    - Added ``is_scheduled`` to :meth:`~pyrogram.Client.get_chat_history`.
 - Added new parameter ``client_platform`` to :obj:`~pyrogram.Client`.
-- Added ``is_scheduled`` to :meth:`~pyrogram.Client.get_messages`.
-- Added ``is_scheduled`` to :meth:`~pyrogram.Client.get_chat_history`.
 - PR from upstream: `1403 <https://github.com/pyrogram/pyrogram/pull/1403>`_.
 - Added ``story`` to :obj:`~pyrogram.types.ExternalReplyInfo`.
 - Added ``story_id`` to :obj:`~pyrogram.types.ReplyParameters`.

diff --git a/docs/source/topics/message-identifiers.rst b/docs/source/topics/message-identifiers.rst
@@ -110,6 +110,5 @@ Megagroups behave differently::
 The group has its own message counter.
 Each user won't get a copy of the message with their own identifier, but rather everyone sees the same message.
 
-# TODO
-
-Things get even messier in Scheduled Messages history section. todo blah blah, try to copy documentation from somewhere..
+For scheduled messages, the message counter instead belongs to the peer itself.
+Bots cannot schedule messages in Telegram, and only users can schedule messages.