Guys! Server survive?

[isopen]

Suppose.

Example:

• Open N+ threads with open clients.
• Further increase the load severalfold. For example: simple sampling operations from chats, etc. Well. Output standard attack.

Are you blocking by headers? But! What if it goes with many nodes. Against this there is what?

[isopen]

Most likely there will be a message with multiple authorization under the same number. It's not clear how the system will behave if the numbers are different but it's already harder. Authorization requests are not clear how to track. There can be a lot of them.

N clients will be connected to tdlib without an authorization request. But! There is a request td_execute({'@type': 'getTextEntities', 'text': '@telegram /test_command https://telegram.org telegram.me', '@extra': ['5', 7.0]}) (perhaps it does not go up to the server but the internal tdlib for checking the library)

It remains only to send an authorization request from different customers. Also td_send({'@type': 'getAuthorizationState', '@extra': 1.01234}) Onion routing or garlic routing and kapets.

Probably something in this spirit i2p

I'm interested in the technical side of the question. How you deal with it :)

[isopen]

Perhaps this is solved by the parameters api_id and api_hash