next-sanity VS telegram-bot-api

Oh nice! For some reason I kept getting referred to with every search: https://github.com/sanity-io/next-sanity

To interact with the Sanity backend, we'll use the Sanity.io toolkit for NextJs, sanity-next. Add it using the following command.

Is not that hard, they have amazing documentation about it: https://core.telegram.org/bots

You can make authorization via Telegram another way. It works. But today we want to do the classic OAuth Authorization. Before you begin, you need to create a Telegram bot and obtain your bot token. You can do this in @BotFather in Telegram. For more information on initiating a bot, read the Telegram Bot API documentation: https://core.telegram.org/bots

Absolutely possible. Here's the github page to the Telegram bot API. You would just need to check for incoming messages, check the body of the message for a word or phrase, and then send a message back with a photo or gif and an encouraging message.

Creating a Telegram bot is fun: there's no website, no sign up, no forms — you just use a... bot. Yes, a bot that creates bots. It's called the BotFather 😂

Telegram has a bot API server that provides API to control the bots and get updates. Their own instance has some restrictions like you cannot download files bigger than 20MB. So, using a self hosted bot API server, you can overcome those limits.

General Bot Platform Overview

$ curl -4 -v https://api.telegram.org * Trying 149.154.167.220:443... * TCP_NODELAY set * Connected to api.telegram.org (149.154.167.220) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): * TLSv1.3 (IN), TLS handshake, Certificate (11): * TLSv1.3 (IN), TLS handshake, CERT verify (15): * TLSv1.3 (IN), TLS handshake, Finished (20): * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.3 (OUT), TLS handshake, Finished (20): * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 * ALPN, server accepted to use h2 * Server certificate: * subject: CN=api.telegram.org * start date: Mar 24 15:21:45 2022 GMT * expire date: Apr 25 15:21:45 2023 GMT * subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org" * issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2 * SSL certificate verify ok. * Using HTTP2, server supports multi-use * Connection state changed (HTTP/2 confirmed) * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0 * Using Stream ID: 1 (easy handle 0x555fdb2de2f0) > GET / HTTP/2 > Host: api.telegram.org > user-agent: curl/7.68.0 > accept: */* > * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * old SSL session ID is stale, removing * Connection state changed (MAX_CONCURRENT_STREAMS == 128)! < HTTP/2 302 < server: nginx/1.18.0 < date: Tue, 18 Oct 2022 00:00:24 GMT < content-type: text/html < content-length: 145 < location: https://core.telegram.org/bots < strict-transport-security: max-age=31536000; includeSubDomains; preload < access-control-allow-origin: * < access-control-allow-methods: GET, POST, OPTIONS < access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection < 302 Found 302 Found nginx/1.18.0 * Connection #0 to host api.telegram.org left intact

It's done via bots, which let you add clickable options to posts. Here's an FAQ on bots: https://core.telegram.org/bots