The timeline feed's declaration: its defaults, its wire request and how an
answer continues the cursor. A feed screen takes these into its own
declaration's request and cursor (ScreenFeedSource), so the screen
sends the one recorded wire and owns only where a page's entries are and
what one entry is.
The two forms this request has are Android wires, selected by the app
profile's MobileApplication.launchWire: the 448 form and the 451 form
(the personalization flag, is_non_feed_surface and the extended
session_level_signals block). The iOS 451 app sends a different feed form
— no include_personalization_features and its own session_level_signals
set — which this brick does not model; an iOS profile does not set the
member.
The timeline feed's declaration: its defaults, its wire request and how an answer continues the cursor. A feed screen takes these into its own declaration's
requestandcursor(ScreenFeedSource), so the screen sends the one recorded wire and owns only where a page's entries are and what one entry is.The two forms this request has are Android wires, selected by the app profile's
MobileApplication.launchWire: the 448 form and the 451 form (the personalization flag,is_non_feed_surfaceand the extendedsession_level_signalsblock). The iOS 451 app sends a different feed form — noinclude_personalization_featuresand its ownsession_level_signalsset — which this brick does not model; an iOS profile does not set the member.