[2] Telegram library/API on .NET.

[q00Dree]

You should research already implemented Telegram bots and even more bots aggregators on .NET and realize how they subscribes and aggregates messages from multiple channels.

Our bots must can:

1. Understand commands (maybe we should implement syntax tree analyzer to execute input commands).
2. Subscribe on channel.
3. Unsubscribe from channel.
4. Check every new news on subscribed channels and aggregate only ones which are match the rules.

[DeiLux]

чет найти никак не могу как подписывать бота к чужому каналу, это вообще реально ? https://github.com/TelegramBots/Telegram.Bot

[DeiLux]

вот еще нашел ответ, боты не могут подписываться на каналы https://qna.habr.com/q/456621

[q00Dree]

Hm, looks like our main task is impossible. We should find another way how we can aggregate news...

[q00Dree]

Look at description of this repository https://github.com/parotikov/telegregator. This guy seeked the same goal.

[q00Dree]

We need real telephone number and register new user - bot. You should research in this way.

[q00Dree]

Maybe this one https://github.com/sochix/TLSharp

[q00Dree]

Or this one https://github.com/wiz0u/WTelegramClient

[q00Dree]

Looks like it's what we want

[DeiLux]

это же клиент, а не бот (BotFather)

[q00Dree]

это же клиент, а не бот (BotFather)

I don't think so, bot is not only BotFather, we can use client to create bot as user. It allows as the ability to subscribe on channels and so on, which are common bot can't do without concrete permissions...

[q00Dree]

Same for VK API. User API is more useful and have no constrains like admin role in chat and so on, but at the same time it's not a human, it's a bot which uses client api/code and registered as client(human).

[DeiLux]

Посмотрел эти репозитории, они по ip подключатся к телеграму, +- как мы бота подключали к чату