acetheking987/bsky-social-app
1
0
Fork 0
Code Issues Actions Packages Projects Releases 1 Wiki Activity

note why the public chat client skips the network-aware fetch

Browse Source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Samuel Newman
2026-08-03 16:30:03 +03:00
parent 72162c1544
commit 38042dcc02
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/state/queries/join-links.ts
+5
View File
@@ -166,6 +166,11 @@ let publicChatClient: Client | undefined
* so no `atproto-proxy` header is involved. A single module-level instance, * 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 * because there is no session to scope it to and reconstructing it per call
* would be waste. * 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 { function getPublicChatClient(): Client {
return (publicChatClient ??= createLexClient({service: CHAT_SERVICE})) return (publicChatClient ??= createLexClient({service: CHAT_SERVICE}))