Skip to content

Conversation

@KnorpelSenf
Copy link
Contributor

Did not read your template, sorry, just wanted to fix this one word.

If you'd like to make sure that the Webhook request comes from Telegram, Telegram
recommends using a secret path in the URL, e.g. https://www.example.com/<token>. Since
nobody else knows your bot's token, you can be pretty sure it's us.
nobody else knows your bot's token, you can be pretty sure it's them.
Copy link
Member

@harshil21 harshil21 May 7, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
nobody else knows your bot's token, you can be pretty sure it's them.
nobody else knows your bot's token, you can be pretty sure it's Telegram.

I would change it to Telegram since it makes more clear who it is, rather than us (PTB or Telegram?) and them (Telegram or the attackers?)

But let's see what the other maintainers think

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm fine with both.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please @ me when you have agreed on something, I'm fine with both, but slightly prefer them because it's been mentioned several times in the sentence before that we're talking about Telegram.

@Bibo-Joshi Bibo-Joshi changed the base branch from master to doc-fixes May 7, 2022 18:06
@Bibo-Joshi Bibo-Joshi merged commit 3401b48 into python-telegram-bot:doc-fixes May 8, 2022
@Bibo-Joshi Bibo-Joshi mentioned this pull request May 8, 2022
5 tasks
@KnorpelSenf KnorpelSenf deleted the patch-1 branch May 8, 2022 11:23
@github-actions github-actions bot locked and limited conversation to collaborators May 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants