Cute blog post. I would suggest to not use wrappers for building Telegram bots, and instead learn how it actually works. State management can be complex when building menus.
yeah I've built a bunch of small and medium bots and every time I've tried to use a library I've run into way more problems than just using the telegram API directly, which is definitely one of the nicer APIs I've used
And between the really good docs and thousands of community wrappers, the agents can usually one-shot complex Telegram-API related features too.
Cute blog post. I would suggest to not use wrappers for building Telegram bots, and instead learn how it actually works. State management can be complex when building menus.
yeah I've built a bunch of small and medium bots and every time I've tried to use a library I've run into way more problems than just using the telegram API directly, which is definitely one of the nicer APIs I've used
And between the really good docs and thousands of community wrappers, the agents can usually one-shot complex Telegram-API related features too.
Will definitely give that a try next time
> Not everything has to be AI
well, not everything has to be workers or serverless :)
Haha. Been enjoying developing on the Workers platform. Can't go back now, lol.
Interesting, reminds me of building bots with Lambdas and GCP Cloud functions when they were a thing.
I find sharing current location a bit of an overkill to get a user‘s timezone. What‘s your take on that?
Yes. It is a bit overkill. But I did not find a "better" and reliable way to get timezone from the user.
[dead]
[dead]
[flagged]