Variable DirectThreadDetailsSchemaConst
DirectThreadDetailsSchema: Union<
readonly [
Struct<
{
is_group: Literal<false>;
peer_user_fbid: optionalKey<String>;
peer_user_id: optionalKey<String>;
thread_title: String;
thread_v2_id: String;
},
>,
Struct<
{
is_group: Literal<true>;
lead_user_id: optionalKey<String>;
thread_title: String;
thread_v2_id: String;
},
>,
],
> = ...
What the thread details hub is opened with and keeps, a sum on whether the thread is a group: each kind holds only the facts that exist for it.
users[0]), which the thread screen carries from its answer — one source for both ids:peer_user_idis thepkthe sharing-info query sends andpeer_user_fbidthe Facebook-side id (fbid_v2, the inbox row's person) the profile-updates query sends (run-direct-feed-theme92); the sharing-info answer carries neither. The peer is also the person the hub asks about when it comes back in front.lead_user_id: the person the hub asksGetUserSharingInfoabout when it comes back in front (the 451direct-actions-group105 names the group's first member). It sends no profile updates, so it holds no Facebook-side id.