26995
Welcome to Bot Talk! 😌 Be nice 🗣 Please use English so everyone can participate 🤖 Keep the topic on bot development ⚠️ Keep media posts like GIFs and stickers to a minimum ❌ Don't add bots to the chat More info - https://t.me/BotTalk/110874
you already answered
yes you can implement rate limits in your bot.
no, if you tracking activities in your bot. If you track activities in other channels and groups, that is scraping = subject to ban.
Читать полностью…
A good and a short username is the first step
Читать полностью…
board chess use rich buttons or what is that
Читать полностью…
you can still showcase it to your friends like this
Читать полностью…
its miniapp not rich text, i or maybe we want to experience rich text chess with friends
Читать полностью…
text = "Hello <b>{name}</b>"
text = text.replace("{name}", "Samrat")
# Send with parse_mode=HTML
I told unmute group.. Not unmute a user.. And sorry for misunderstanding.
It's just an example.. Sometimes we need some deley like 10 second to some hours. So how we will do that?
Then I'd keep the Mini App and its API on managed serverless hosting, ideally under one origin, and let the API own the database. No VPS to maintain, and you avoid trying to turn chat updates into HTTP requests. The bot's update handlers can still handle /start and buttons separately.
What is the Mini App meant to do — mainly per-user settings, or shared data such as bookings/orders? That decides whether a tiny API is enough and where you need transaction handling.
The docs do leave a gap here: they advertise Mini App backends, but document update handlers and outbound fetch, with no public HTTP entry point or static-file hosting. Only schema.js and JS modules are deployed. I wouldn't treat that as a documented way to expose a browser API yet.
sendData isn't a general replacement: it's for Mini Apps opened from a reply-keyboard button, and sending closes the Mini App. For reads/writes while the app stays open, an HTTPS frontend + your own API validating initData is the straightforward route. The update handlers can remain on Telegram, but don't assume the external API can directly access its built-in database.
Are you trying to share that built-in database with the Mini App, or mainly avoid managing a VPS?
https://core.telegram.org/bots/serverless
https://core.telegram.org/bots/webapps#keyboard-button-mini-apps
For the one-hour user mute in a supergroup, Telegram can handle expiry itself: restrictChatMember with until_date set to now + 3600 (Unix seconds), assuming the bot has permission to restrict members. That part doesn’t need a cron job. Are you unmuting individual members, or reopening the whole group? Deleting a normal message after 10 seconds is a separate scheduling case. https://core.telegram.org/bots/api#restrictchatmember
Читать полностью…
when someone creates a GIF using my bot in a group chat i track it, should i stop? I'm doing this to implement rate limits and anti abuse behavior.
Читать полностью…
Is keeping track of who is using the bot and their activity illegal? i keep track of who joined and when they created something on mine.
Читать полностью…
Finding users has been more challenging so far
Читать полностью…
Can you please recommend me any groups to promote my bot since I'm past the development phase
Читать полностью…
guys, this not a place to play with bots
Читать полностью…
the problem with multiplayer is that the bot will have to flip every turn
which might not be a good experience for both users
There are still bugs in the Serverless web app interface.
Читать полностью…
Got it — delayed actions in general. Telegram Serverless currently documents update handlers, but no scheduled-job API. A practical route is an external delayed-job queue that calls the Bot API when the job is due. Saving a timestamp and checking it on the next update won’t work if the chat stays quiet. I wouldn’t rely on keeping a handler asleep for an hour.
Читать полностью…
Pages covers the frontend. The missing piece for fetch() is a Pages Function: that handles the HTTP request and validates initData. Plain static Pages + Telegram update handlers alone still leaves that API gap. You can add Functions to the Pages project without a VPS: https://developers.cloudflare.com/pages/functions/
Читать полностью…
Meaningless AI generated drivel. Good god.
Читать полностью…
Mini App + own backend API on Telegram Serverless — possible?
Trying to figure out if Telegram Serverless can work for a bot that has a Mini App attached to it. The web page needs to call some kind of backend to read/write data, with the request checked against initData.
Reading through the docs (core.telegram.org/bots/serverless), all I see is handlers/<type>.js that fire on Telegram Updates — messages, callback queries etc. Nothing that looks like a normal HTTP endpoint the web page itself could hit with fetch(). Also don't see anything about serving the actual HTML/JS files for the Mini App.
So a few things I'm not sure about:
Is there some way to expose an endpoint for the Mini App to call directly, or is that just not a thing here?
Is the actual intended flow that the Mini App only talks back through sendData() (so it shows up as a message update with web_app_data), instead of calling a normal API?
And where does the Mini App's html/js/css itself live if Serverless only takes .js modules — still need something like Cloudflare Pages / GitHub Pages on the side just for the frontend?
Maybe I'm missing something obvious, but from what I can tell Serverless is built for chat-driven bots and doesn't really cover the Mini App + API case. Would appreciate it if someone who's actually built one confirms or corrects me.
cloning is easy
if i were to design it from scratch that would be a different story