telexide VS teloxide

This has been the first time I had the need to work with a fork of a rust project. In fact, I started creating RaF depending upon telexide but the project was abandoned and it was lacking certain features I needed (and it has some bugs too - I created a pull request but it has been completely ignored :( ).

I'm using teloxide, which is a crate for building Telegram bots. I have a small Telegram bot running on my Raspberry Pi, and since it's very slow to compile, I'm trying to cross compile it from my Windows machine, with no luck.

I do completely agree with your advice of using `Arc`s. But unfortunately, sometimes it gets very tedious to deal with all these `Arc`s: https://github.com/teloxide/teloxide/blob/ec1d41220c51872cf9....

It also blurs the advantage of Rust as a lifetime validation tool if you use reference counting anyways. But it seems that it's the only viable approach for async at the moment.

A Telegram bot built with Rust Telegram bot framework Teloxide, used to provide support to new users discovering our network, and to help them navigate through our channels of information by using various commands to interact with and find a job as fast as possible without need for visiting /jobs page from our website.

There is https://github.com/teloxide/teloxide though, maybe there is a confusion? It's actively maintained?

This is prototype and we plan to include more features. The bot is built with Rust Teloxide framework and we plan to deploy more Rust code for our production code, web pages and end points.

We also built a Telegram bot with Rust Teloxide framework and will deploy this week and show that is is written in Rust also.

Working on teloxide, a Telegram bots framework for Rust.

As was said earlier, for visibility purposes, gRPC client is also a Telegram bot. To implement the bot, teloxide library was used.

You can also make some social media bots with Rust