teloxide VS substrate-open-working-groups

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

Polkadot Developer Community - Official community forum to discuss Substrate, PolkadotJS, and building cross-chain dApps.

And of course you can always develop your own blockchain with Substrate to support it.

A great framework for building your own blockchain, and use numerous off-the-shelf modules, with Substrate - https://substrate.dev/

If you're interested in developing yourself, check out substrate.dev.

Assuming you are working through the substrate.dev tutorials I have just had this same problem as worked around it by reverting the node template to the `polkadot-v0.9.25` tag.

Well. Polkadot created substrate (substrate.dev) which is a framework for building a blockchain, with a lot of general components to make it easy to "plug-and-play" your customizable blockchain. I tried using their "Getting Started" guide to spin up "my own blockchain", it was done within an hour or so.

Check out https://substrate.dev/ !

Substrate is not a chain; it's the default address style, named after the Substrate development framework which virtually all (if not all) parachains are currently built with. https://substrate.dev/

Do contact the Substrate project (basis of the Polkadot/Kusama project), which is based in Berlin. You can contact them on their channel (see their website on http://substrate.dev), they're friendly and many of them are native German speakers.