1011
Telegram Bot Development. Not Bot Recommendations or Bot Requests or Bot Advertisement or Bot Developer Recruitment. (See @BotList, @BotListChat.) Log: @ou_ch Rules: /rules@oubot
And that's why the first feature I added to rose was deleting guest mode messages
Читать полностью…
New spamming technique unlocked: Using guest mode on bots and deleting original message
Читать полностью…
This is the confusing part. Perhaps you can share some code?
Читать полностью…
What's menu builder bot?
This isn't the support channel for a specific bot. It's support for bot development
Rules for Bot Development:
1. English discussion of bot development only.
2. No spam, advertisement, requests, or spoon-feeding.
3. RTFM: Always consult documentation and Google first.
4. Don't ask to ask; just ask.
5. Bot Development, not Recommendations or Advertisement or Developer Recruitment. (see @BotList, @BotListChat)
If you need support with it, someone in this group might be happy to help
Читать полностью…
if you have further questions, feel free to ask.
Читать полностью…
Hello Everyone
I want help anyone can help me about python code
Rules for Bot Development:
1. English discussion of bot development only.
2. No spam, advertisement, requests, or spoon-feeding.
3. RTFM: Always consult documentation and Google first.
4. Don't ask to ask; just ask.
5. Bot Development, not Recommendations or Advertisement or Developer Recruitment. (see @BotList, @BotListChat)
Trying to follow "the limits" is only going to cause you issues - the only way to handle it right is to respect the floodwaits
Читать полностью…
Bots aren't intended for large scale notifications/broadcasts. There's no trick, it's just not what telegram want bots to do
Large bots can pay in stars to go above the limits - there's a flag on sendmessage to allow you to do that
I really need to switch away from self hosted Group Butler in my groups
Читать полностью…
Rules for Bot Development:
1. English discussion of bot development only.
2. No spam, advertisement, requests, or spoon-feeding.
3. RTFM: Always consult documentation and Google first.
4. Don't ask to ask; just ask.
5. Bot Development, not Recommendations or Advertisement or Developer Recruitment. (see @BotList, @BotListChat)
Apologies for being unclear; I meant to clarify whether or not it was missing from Botfather after being created. (unless the new managed bot stuff doesn't even have the user create the bot first. i haven't messed with that.)
Читать полностью…
YES BRO, I CAN'T SEE CAPTCHA IN MENU BUILDER BOT TO ADD IN MY BOT
Читать полностью…
5. Bot Development, not Recommendations or Advertisement or Developer Recruitment. (see @BotList, @BotListChat)
Читать полностью…
Good day, I'm try to add CAPTCHA in order to verify the bot users but I can't see it in my botfather and menu builder bot. Please help me out 🙏
Читать полностью…
lucky for you, the pin is specifically about learning Python & Telegram bot development using Python
Читать полностью…
5. Bot Development, not Recommendations or Advertisement or Developer Recruitment. (see @BotList, @BotListChat)
Читать полностью…
that sounds very in character of telegram's practice
Читать полностью…
That’s an interesting point about Stars, thanks! However, our recent tests show a slightly different picture.
We managed to successfully deliver tens of thousands of messages with fewer than 100 errors (429/Flood Wait). So it clearly works, but we’re still not hitting the consistency we’re aiming for.
We seem to be hitting a specific "barrier" or filter even when strictly following the limits with a safety margin (e.g., batch size of 25). We're trying to figure out if this is an algorithmic spam filter triggered by message patterns, or if there's another underlying technical reason we're missing.
Has anyone noticed if message variety (unique content per user) helps bypass this "barrier"?
Hi everyone! 👋
We’re running into some weird behavior with Telegram's limits and could use some advice.
We (the team at BQbot) are implementing a notification system for our beauty salon partners. Even though we’re staying well within the official 30 messages per second limit, we keep hitting FloodWait errors.
We’ve tried several test runs with different delays between batches, but the results are super inconsistent. The FloodWait triggers even when we have significant pauses between outgoing messages.
A few questions for those who’ve dealt with this:
1. Are there any "hidden" rate limits for proactive notifications (bots messaging users first) that aren't in the official docs?
2. Does Telegram trigger spam filters based on message similarity, even if we’re under the global rate limit?
3. Any tips on the best batch size or "cool-down" strategy to avoid these random blocks?
Would appreciate any insights or "war stories" from anyone who’s scaled a notification bot recently. Thanks!