Skip to content

fix(search): route logged-out search to the Bluesky appview - #173

Open
rishibalakrishnan wants to merge 2 commits into
mainfrom
fix/search-routing-logged-out
Open

fix(search): route logged-out search to the Bluesky appview#173
rishibalakrishnan wants to merge 2 commits into
mainfrom
fix/search-routing-logged-out

Conversation

@rishibalakrishnan

Copy link
Copy Markdown

Search reads can be routed to the Bluesky appview behind the search_appview:route flag. The atproto-proxy header that implements that routing is only honored by a PDS, so a logged-out agent — which talks to an appview directly — dropped the header and kept every search on the home appview no matter how the flag was set.

Logged-out search, actor search, and typeahead now use a Bluesky-hosted agent when the flag routes to Bluesky. Authenticated calls are unchanged and keep using the proxy header, so results stay session-scoped. getSuggestedFeeds passed its own headers object and never picked up the routing opts; it now merges them.

Test plan

  • Signed out: search posts, search accounts, and composer/typeahead all return results
  • Signed in: same surfaces still return results, with the user's mutes/blocks applied
  • Flip search_appview:route off and confirm both states fall back to the home appview
  • Explore tab suggested feeds render signed in and signed out

The atproto-proxy header is only honored by a PDS, so a logged-out agent
talking to the appview directly kept its search reads on the home appview
regardless of the routing flag. Use a Bluesky-hosted agent for those calls,
and apply the routing opts to getSuggestedFeeds, which set its own headers
and never picked them up.
@github-actions

Copy link
Copy Markdown
Old size New size Diff
9.11 MB 9.12 MB 293 B (0.00%)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant