Jannik

@andrew-ld That's why it must be enabled explicitly. It should not be a default behavior

Sorry that I'm currently not working on this, have a bunch of exams in February. I will have a look at it again when I'm done with them.

I first tried to create a token with the user_id after the login, but I couldnt get it to work "moving" the tdlib instance to a new token after it...

Okay, I was not up to date with that, using tgcalls would be fine

It would be disabled by default of course and can only be activated with a command line comment. Allowing calls would let this api really stand out compared to most...

I would not have any live communication from the server to the client. Just normal requests to play audio or start/stop/download the recording of the incoming audio/video stream.

Or maybe the possibility to set a redirect via command line parameter? We could set the redirect on our publicly hosted instances without interfering with the default behaviour

@Cavallium Having a hosted webpage and a redirect doesn't make much sense. If someone wants to redirect he could simply use a html redirect, has the same effect

@Cavallium I don't like the idea of hosting a homepage on the bot api. We would need to pack all css and other static content like images into one big...