From 38042dcc0262ad1fec81757fe737e09b6a00fb5c Mon Sep 17 00:00:00 2001 From: Samuel Newman Date: Mon, 3 Aug 2026 16:30:03 +0300 Subject: [PATCH] note why the public chat client skips the network-aware fetch Co-Authored-By: Claude Fable 5 --- src/state/queries/join-links.ts | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/src/state/queries/join-links.ts b/src/state/queries/join-links.ts index e53edc0291..e5dbbc9bed 100644 --- a/src/state/queries/join-links.ts +++ b/src/state/queries/join-links.ts @@ -166,6 +166,11 @@ let publicChatClient: Client | undefined * so no `atproto-proxy` header is involved. A single module-level instance, * because there is no session to scope it to and reconstructing it per call * would be waste. + * + * Unlike the public appview client this does NOT wrap `networkAwareFetch`, + * matching the plain-fetch behavior of the ad-hoc agent it replaces: a + * logged-out link resolution failing says nothing useful about the session's + * reachability, so it should not move the app-wide network signal. */ function getPublicChatClient(): Client { return (publicChatClient ??= createLexClient({service: CHAT_SERVICE}))