inquire
Field notes/Modules
Blue and grey network cables plugged into a patch panel10.05Field note · Modules
#telegram#modules
1 min readInquire desk

Telegram lookup, two paths instead of one

Added an external-index lane ahead of the MTProto session so an empty session result stops being the end of the road.

One call was deciding too much

Phone-to-Telegram used to be a single MTProto call: import the contact, read back the entity, done. When Telegram returned an unoccupied number that was the whole answer, which is wrong more often than it should be, because an index that captured the number at a different time may still hold the account.

Index first, session second

Now the check tries the external index first when it is configured, then the session, and reports which path produced the hit. Both lanes are labelled in the result so you can tell a session hit from an index hit without guessing.

No new account, no scraping

No new account or scraping. If the index is not configured it is skipped silently and the session path runs exactly as before.

IQ

The Inquire desk

Build notes from the console and the lanes behind it. Written when something actually changes, with the numbers attached.

Related notes

View all

Explore more from Inquire

You already know the first question.

One field, the whole catalogue behind it, and every answer filed with the module that produced it.