why#

designing lexicons are weird

these are the XRPC methods i think are required for a minimal functioning bluesky index to function and pass around data

some of the methods here reuse existing app.bsky.* XRPC methods, but some are custom under the party.whey.* namespace.

this is done because i believe that it is expensive to force every single node to return inlined / hydrated responses, when the view server that ingests and composites the final view might not even use the provided inlined / hydrated data in the first place.

and so, i created "Partial" variants of existing app.bsky.* methods, that allow for "skeleton" responses. specifically, for all methods relating to posts, they are allowed to return "PostViewRef" objects instead of the hydrated "PostView" object. PostViewRef is currently just identical to a strongRef and i am not yet certain if we should add more optional fields to it.

i do not think that the current lexicons are perfect, but they are good enough that i can continue development of other parts of the skylite system for now