nikat / mtproto2json Goto Github PK

Hi there again. Thanks for your program, it's really indispensable for the job I'm doing at the moment.

@milch @lattenwald
I need a little advice. I used the same session ID and auth key in production and on my local dev server and noticed that the production stopped working with these messages:

Timeout, no rpc_response, I am deleting this: {'_cons': 'account.updateStatus', 'offline': {'_cons': 'boolFalse'}}
Timeout, no rpc_response, I am deleting this: {'_cons': 'account.updateStatus', 'offline': {'_cons': 'boolFalse'}}
...

Seems like Telegram just started to ignore requests from the production server once I started to use this auth on the development one. Is this correct? If I generate a different token for development and use the separate tokens, should it work?

I just want to make sure I figured things out because unlike Bot API, the client API is somewhat more unexpected.

Followed the instructions in README. After successful authentication, I'm trying to get the dialog list as you tell with {"message":{"_cons":"messages.getDialogs","offset_date":0,"offset_id":0,"offset_peer":{"_cons":"inputPeerEmpty"},"limit":0}}.

The result:

I'm trying to get my development server working while the production is running. I'm using different tokens. On the development I'm getting these responses for any request:

{"id": 0, "message": {"_cons": "bad_msg_notification", "bad_msg_id": 6532164331258096284, "bad_msg_seqno": 3, "error_code": 17}}

Telegram docs suggest that error_code == 17 has something to do with msg_ids. They tell that "the client time has to be synchronized, and the message re-sent with the correct msg_id". Anyone knows what does it mean?

@milch @lattenwald

Hi,

First of all let me thank you for this project, it's helped me a lot in integrating Telegram in a personal project of mine.

My issue is, as the title says, that eventually I just stop receiving updates. Sometimes a message sent to my account will be delayed for 30s or more and arrive together with another message that was sent later. Do you know if there is any way to ensure that I can keep receiving updates? I tried sending a getDialogs every 60s or so but that doesn't always work.

This error eventually appears when I stop my production server and launch the development one on my laptop. Have no idea what's the reason, but it usually disappears by itself after some time (i.e. 30 minutes).
Seems that it disappears after restarting my server like 8 times.

README tells:

NOTE: mtproto2json will be updated to support MTProto2.0 in Jan 2018.

Is it already updated?

If not, how long will they support the old protocol?