Support for TDLight extended API

[a3kov]

Something to consider.
There's modified API gateway https://github.com/tdlight-team/tdlight-telegram-bot-api that supports additional methods only available in MTProto originally.
I think it could be a nice addition to this project. Not all people will run this gateway, so the feature to include the unofficial methods would have to be opt-in setting

[rockneurotiko]

I had no idea about this project. I think it needs some investigation on how it would be integrated, because it modifies many existing methods.

[a3kov]

Yeah. It's not so simple. Also new methods have different quotas

[smaximov]

Is there a need for a scraper for TDLight API if they already provide an OpenAPI schema?

[a3kov]

I noticed that too, but it's up to you (since we already have this flow integrated might be easier to keep using that, I don't know).

[rockneurotiko]

I'm not really sure about that too, because if ExGram end up with implementation for TDLight, it would be easy to have it here, but then the purpose and scope of this project would change.

[a3kov]

This is a complex topic indeed. If there was a native MTProto 2.0 implementation for Erlang/Elixir I woudln't even bother - original Bot API is too limited.
But then there are issues with MTProto too, such as lack of HA setup. You have to implement your own monitoring and manual failover in case the gateway crashes, or becomes unavailable otherwise. At least with Telegram servers it's their own problem.
I guess if somebody doesn't need to lookup users and download/upload big files, they would be better off using the official Bot API. With all it's limitations, it's still more robust and simple solution.