You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ten app.bsky.unspecced.* lexicons are present upstream but missing from ATProtoKit, spanning two product surfaces: the post thread v2 algorithm and the Explore/onboarding per-rail user suggestions. Each maps cleanly onto an already-wrapped unspecced sibling, so the additions are mechanical. (getAgeAssuranceState and searchStarterPacksSkeleton were dropped from this request — they are already wrapped in ATProtoKit.)
Pain points
Onboarding rail (getOnboardingSuggestedUsersSkeleton + getSuggestedOnboardingUsers) — no typed access to the onboarding "who to follow" surface.
Post thread v2 (getPostThreadOtherV2 / getPostThreadV2) is the new threaded view algorithm. Clients on the typed pipeline are stuck on the v1 app.bsky.feed.getPostThread.
Explore per-rail suggestions — Bluesky's Explore tab has separate rails (Discover / Explore / SeeMore) each backed by a dedicated getSuggestedUsersFor* (+ Skeleton) endpoint. Without these, third-party clients can only show the generic getSuggestedUsers rail.
Considered Alternatives
Raw XRPC per call site — works but every consumer reimplements the same wrapper shape, and unspecced host routing has to be handled correctly each time.
As we discussed, I've filed the missing features as separate feature requests for tracking. None of them are urgent on my end, so I plan to follow up on each as the need actually arises.
Given that ATLexiconC is on the horizon, please feel free to handle these at your own pace — there's no rush, and it may well make sense to let ATLexiconC cover some of them rather than typing everything out by hand. I'm happy to help and provide corrections whenever it's useful.
Activity
KC-2001MS commentedon Jul 17, 2026
As we discussed, I've filed the missing features as separate feature requests for tracking. None of them are urgent on my end, so I plan to follow up on each as the need actually arises.
Given that ATLexiconC is on the horizon, please feel free to handle these at your own pace — there's no rush, and it may well make sense to let ATLexiconC cover some of them rather than typing everything out by hand. I'm happy to help and provide corrections whenever it's useful.