Skip to content

/whoami: reply_parameters instead of deprecated reply_to_message_id - #106

Merged
remdex merged 1 commit into
LiveHelperChat:masterfrom
mysubcult:fix/deprecated-reply-to
Oct 26, 2026
Merged

remdex merged 1 commit into
LiveHelperChat:masterfrom
mysubcult:fix/deprecated-reply-to

Conversation

@mysubcult

@mysubcult mysubcult commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

reply_to_message_id is deprecated since Bot API 7.0 in favour of reply_parameters. /whoami was the last place in the extension that still sent it; Telegram still accepts the old field, so this is only a modernisation. (applyLinkPreviewOption() keeps checking disable_web_page_preview on purpose — a caller may still pass it.)

Same reply_parameters form is used in production for replies in operator topics (text and file uploads).

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mysubcult added a commit to mysubcult/telegram that referenced this pull request Oct 26, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@remdex
remdex merged commit 6ed5641 into LiveHelperChat:master Oct 26, 2026
mysubcult added a commit to mysubcult/telegram that referenced this pull request Oct 28, 2026
…al Telegram bots (chat_id_2 = telegram_bot_id, chat_external_first) kept with our reply_parameters

Live incoming webhook / REST API configs are not changed: one visitor bot, existing chats keep their chat ids.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mysubcult added a commit to mysubcult/telegram that referenced this pull request Oct 28, 2026
…ot applied live), what the author rejected

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants