DirectInboxFragment:direct_inbox, the Direct tab (Android 451). The tab's
open is one burst in the app's order:
while the feed is still in front, three queries together — the pending
inbox (the message-requests badge), the Direct privacy settings and the
viewer's Spotify account link (MobileRequestContext.Session plus the
Direct surface's x-msgr-region);
then the tab switch (direct_inbox:2:main_direct, the chain every later
request of the burst carries) and the saved replies (quick_reply/get,
signed with the thread modification token, reply type and viewer);
the recommended-users panel's empty state 1.1 s after the saved replies,
then the inbox snapshot (direct_v2/inbox/) with the Meta AI persona
prefetch (IGDirectFetchKaiPersona, bot_id the Meta AI bot) together
0.49 s later. The inbox screen asks its empty
state a second time when the snapshot's answer lands (10 ms after it);
about 1 s later the search warm start (IGDirectSearchInitiateWarmStartQuery,
the picker's own open on the 1:1 run), and 0.3 s after it the stories
lookup (feed/get_latest_reel_media/) for the people of the stored head.
With a stored head (the app's local inbox store, DirectInboxCache) the
snapshot is the filtered first page after the stored cursor
(prefetch_filtered_first_page), and the person's stories are the stored
threads' participants; without one the snapshot is the initial page
(thread_message_limit=5) and no stories lookup is sent.
mode is a fact of the presented profile, read by directInboxFeed itself:
the 451 profile sends mode=2, the 448 profile sends none.
The answer's seq_id is adopted into the session by the feed producer
(directInboxFeed's request, which decodes and records it), not by this
screen: the app's "New message" and the profile's Message button report it as
the participant lookup's seq_id (the lookup sends
the inbox answer's sequence), and the screens read it from that one source,
never from an input. The post-login launch burst runs the same producer, so a
session that never opened this tab still holds the number.
DirectInboxFragment:direct_inbox, the Direct tab (Android 451). The tab's open is one burst in the app's order:MobileRequestContext.Sessionplus the Direct surface'sx-msgr-region);direct_inbox:2:main_direct, the chain every later request of the burst carries) and the saved replies (quick_reply/get, signed with the thread modification token, reply type and viewer);direct_v2/inbox/) with the Meta AI persona prefetch (IGDirectFetchKaiPersona,bot_idthe Meta AI bot) together 0.49 s later. The inbox screen asks its empty state a second time when the snapshot's answer lands (10 ms after it);IGDirectSearchInitiateWarmStartQuery, the picker's own open on the 1:1 run), and 0.3 s after it the stories lookup (feed/get_latest_reel_media/) for the people of the stored head.With a stored head (the app's local inbox store,
DirectInboxCache) the snapshot is the filtered first page after the stored cursor (prefetch_filtered_first_page), and the person's stories are the stored threads' participants; without one the snapshot is the initial page (thread_message_limit=5) and no stories lookup is sent.modeis a fact of the presented profile, read bydirectInboxFeeditself: the 451 profile sendsmode=2, the 448 profile sends none.The answer's
seq_idis adopted into the session by the feed producer (directInboxFeed'srequest, which decodes and records it), not by this screen: the app's "New message" and the profile's Message button report it as the participant lookup'sseq_id(the lookup sends the inbox answer's sequence), and the screens read it from that one source, never from an input. The post-login launch burst runs the same producer, so a session that never opened this tab still holds the number.Guide: The Direct inbox