part, because it might be unreliable?
If you see id or Peer or InputPeer in actual request fields, server generally includes the User or Channel object related to them in .users or .chats, but Telegram requests are vast and each has different behavior and can change any time. you need to study each request, in GetFullUser case it's guaranteed to have .users as far as i know tho .chats and .users are generic and client needs to deal with missing objects, that's why they're arrays, they're usually cached in memory seperately in realtime once deserialized before anything else and shared among all open chats by actual Telegram apps and you fetch the peers from pool of them, in telethon case a get_entity
Admin please help
Обсуждают сегодня