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

document the public client labeler asymmetry

Browse Source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Samuel Newman
2026-08-03 16:47:33 +03:00
parent 1f3784fc7b
commit 00af680341
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/state/session/clients.ts
+7
View File
@@ -55,6 +55,13 @@ let publicLexClient: Client | undefined
* {@link agentToLexClient}: there is no session to scope it to, so it lives for * {@link agentToLexClient}: there is no session to scope it to, so it lives for
* the lifetime of the process. Requests go through {@link networkAwareFetch} so * the lifetime of the process. Requests go through {@link networkAwareFetch} so
* public reads feed the app's reachability signal like authenticated ones do. * public reads feed the app's reachability signal like authenticated ones do.
*
* Unlike the public agent it parallels, this client sends neither
* `atproto-proxy` nor `atproto-accept-labelers`. `createPublicAgent` configures
* the app labeler and the proxy header, so a logged-out appview *agent* read
* does carry labelers while the same read through this client does not. A
* consumer that needs moderation labels on public reads must configure labelers
* itself before issuing the request.
*/ */
export function getPublicLexClient(): Client { export function getPublicLexClient(): Client {
return (publicLexClient ??= createLexClient({ return (publicLexClient ??= createLexClient({