telegram-bot-ruby VS typer

Instead of WhatsApp, why not turn this into a Telegram app? Telegram’s APIs are built quite well for this type of thing. You can still do it via voice messages [0] or you can even build what Telegram calls a Mini App [1]. And it’s all very straightforward and free!

[0]: https://core.telegram.org/bots/api#voice

[1]: https://core.telegram.org/bots/webapps

Because the documents are really parsed into data. I have converted almost all of the valid content from the official document page (https://core.telegram.org/bots/api) into JSON format and uploaded it to a separate repository (telegex/api_doc.json). This includes all types, methods, and comments.

From a palette point of view I really like node-red-contrib-telegrambot because it exposes the whole telegram api (https://core.telegram.org/bots/api). Should have you covered for sending and receiving text and voice messages.

You will need to code a bot that can do something like this. You can use basically any (popular) programming language. Check https://core.telegram.org/bots/api for more info.

The Telegram bot API is [here](https://core.telegram.org/bots/api). Check the "introduction to bots" link at the top for instructions on how to create a bot.

var back = InlineKeyboardButton.builder() .text("Back").callbackData("back") .build(); var url = InlineKeyboardButton.builder() .text("Tutorial") .url("https://core.telegram.org/bots/api") .build();

Studying guides and the API documentation. Actually, why are you even asking us, just ask ChatGPT. People obsess too much about how you can break or the fact that it will make up shit when discussing historical facts, but for everything else it's actually amazing. Like a friend who knows a little bit of everything and you just ask them if you don't know how to google the answer.

There is fantastic API documentation to develop your own bot, which you can use to send these kinds of messages: https://core.telegram.org/bots/api

He is probably most well know for creating FastAPI that I taught to some of my clients and Typer that I've never used.

I have been using Typer on every one of my CLI projects which uses Click under the hood. The documentation is fantastic, the CLI app it produces looks great and lets you create things quickly. I high recommend it.

https://typer.tiangolo.com/

Adding CLI capabilities. My preferred library here is typer.

I just heard about this but it seems to be pretty much the type of thing you want and want fast.

Docstrings are for documenting how a function/ class/ method/ module works. Often you don't need to add a docstring to your main function because no one will be importing it to use elsewhere. And if you want it to run as a CLI, then there are better ways to document the available options. For example, typer does most of it for you, or in click you add the help text to the decorator.

Most computing tasks in airflow DAGs are KubernetesPodOperator containing a CLI (Python Typer). It allows us to pass arguments easily to run DAG manually if needed (the new UI to pass arguments to DAG in airflow 2.6 is really nice). Arguments allow us to replay DAG easily (change start / end dates for instance).

So it's basically the main .gitlab-ci.yml file plus a separate Python CI app using Typer for the AWS instrumentation.

Similarly for Typer, which is literally "the FastAPI of CLIs"[1]. Handy to type your `main` parameters and have CLI argument parsing. For more complicated cases, it's a wrapper around Click.

[1] https://typer.tiangolo.com/