Some phone numbers do not search for the user by phone number about td

[levlam]

This is intended behavior. Server may not return the user and prevent abuse of the API.

[DenysSamoiliuk]

This is intended behavior. Server may not return the user and prevent abuse of the API.

tell me, do you know where you can find out about such names, such as a phone number, since the number has been in Telegram for 3 weeks, but we have not used it for 2 weeks, but the search is still not available, and we regularly search for another user everything is fine for sending information, but searching by username does not present any problems, however, I would like to understand these limitations more transparently

[DenysSamoiliuk]

@levlam i get the following in these methods

https://core.telegram.org/method/contacts.resolvePhone

RPCError: 400: PHONE_NOT_OCCUPIED (caused by contacts.ResolvePhone)
at RPCMessageToError (/home/hrederik/WebstormProjects/novait/telegram-web-api/node_modules/telegram/errors/index.js:28:12)
at MTProtoSender._handleRPCResult (/home/hrederik/WebstormProjects/novait/telegram-web-api/node_modules/telegram/network/MTProtoSender.js:546:58)
at MTProtoSender._processMessage (/home/hrederik/WebstormProjects/novait/telegram-web-api/node_modules/telegram/network/MTProtoSender.js:476:15)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at MTProtoSender._recvLoop (/home/hrederik/WebstormProjects/novait/telegram-web-api/node_modules/telegram/network/MTProtoSender.js:424:17) {
code: 400,
errorMessage: 'PHONE_NOT_OCCUPIED'
}

https://core.telegram.org/method/contacts.importContacts

res {
CONSTRUCTOR_ID: xxxx,
SUBCLASS_OF_ID: xxxx,
className: 'contacts.ImportedContacts',
classType: 'constructor',
imported: [],
popularInvites: [],
retryContacts: [ Integer { value: 2570974896n } ],
users: []
}

could you share in more detail the data about the restrictions and if you have any information on how to get rid of them from the number

[levlam]

Both search by phone number and by user name are highly limited. It is not possible to harvest Telegram users using these methods.

[DenysSamoiliuk]

@levlam
for example, I found a user from another number whose phone number is private (only for contacts), and I am not his friend and have no previous conversations, that is, he is completely anonymous for me with privacy settings

user {
  CONSTRUCTOR_ID: xxxx,
  SUBCLASS_OF_ID: xxxxx,
  className: 'contacts.ResolvedPeer',
  classType: 'constructor',
  peer: {
    CONSTRUCTOR_ID: xxxx,
    SUBCLASS_OF_ID: xxxxx,
    className: 'PeerUser',
    classType: 'constructor',
    userId: Integer { value: xxxxx}
  },
  chats: [],
  users: [
    {
      CONSTRUCTOR_ID: xxxx,
      SUBCLASS_OF_ID: xxxx,
      className: 'User',
      classType: 'constructor',
      flags: xxxx,
      self: false,
      contact: false,
      mutualContact: false,
      deleted: false,
      bot: false,
      botChatHistory: false,
      botNochats: false,
      verified: false,
      restricted: false,
      min: false,
      botInlineGeo: false,
      support: false,
      scam: false,
      applyMinPhoto: true,
      fake: false,
      botAttachMenu: false,
      premium: false,
      attachMenuEnabled: false,
      flags2: 16,
      botCanEdit: false,
      closeFriend: false,
      storiesHidden: false,
      storiesUnavailable: true,
      contactRequirePremium: false,
      id: [Integer],
      accessHash: [Integer],
      firstName: 'Vladyslav',
      lastName: null,
      username: 'pc_Vl_6',
      phone: null,
      photo: null,
      status: [Object],
      botInfoVersion: null,
      restrictionReason: null,
      botInlinePlaceholder: null,
      langCode: null,
      emojiStatus: null,
      usernames: null,
      storiesMaxId: null,
      color: null,
      profileColor: null
    }
  ]
}

[levlam]

Everything works as intended.

[DenysSamoiliuk]

@levlam thx