atradio/apps/api/src/connect/ at main · atradio.fm/atradio · Tangled

atradio.fm / atradio

7

A social internet radio platform built on AT Protocol. atradio.fm

atproto radio

7

atradio / apps / api / src / connect /

at main 4 files

Tsiry Sandratraina fix(connect): request the rpc OAuth scope with a did#serviceId audience 19hrs ago

fix(connect): request the rpc OAuth scope with a did#serviceId audience OAuth sessions need an `rpc:fm.atradio.connect?aud=…` scope to mint the service-auth token that authenticates the Connect WebSocket. The audience must be a DID *service reference* (`did:web:api.atradio.fm#atradio_appview`) — atproto's scope parser rejects a bare DID, so the authorization server silently dropped the scope and getServiceAuth failed with ScopeMissingError. - api: add CONNECT_SERVICE_AUD (bare DID + #atradio_appview); the hub verifies the JWT aud against it; /health exposes connectAud; did.json id stays the bare DID. - web: CONNECT_SERVICE_AUD drives the requested scope, client-metadata.json, and the getServiceAuth aud; PermissionBanner keys off the exact scope token; drop the /health aud discovery in favor of the fixed constant. - cli: request the scope and mint the token with the fragmented aud. - also surface the new scope in the re-auth banner (en/fr/pt). Requires re-authentication (log out + in) to mint a session carrying the corrected scope.

19 hours ago

feat: atradio Connect — cross-device remote control Spotify-Connect-style remote control across web + CLI. Every logged-in client opens a WebSocket to a new hub in apps/api, is grouped by account DID (verified via atproto service-auth JWT), and can list and control the other devices on the account. - api: WebSocket Connect hub (/connect) with per-DID device registry, command routing, presence tracking, Redis cross-instance relay, and a did:web service document. Service-auth JWTs verified with @atproto/xrpc-server + @atproto/identity. - web: device picker (navbar) + bottom "Playing on …" banner, transport routing to the selected remote, transfer-here/there, and WS-driven deletion of the actor.status record when no player is online. - cli: remote module (tokio-tungstenite) making the TUI both controllable and a controller, a device-picker overlay + text indicator, a headless `--no-tui` daemon mode, and a settings.toml-configurable device name. - tests: hub integration tests (ws) + web routing/transfer + device helper tests; new GitHub Actions workflow runs web + api suites. - i18n: new `connect` namespace for en/fr/pt.

20 hours ago

feat: atradio Connect — cross-device remote control Spotify-Connect-style remote control across web + CLI. Every logged-in client opens a WebSocket to a new hub in apps/api, is grouped by account DID (verified via atproto service-auth JWT), and can list and control the other devices on the account. - api: WebSocket Connect hub (/connect) with per-DID device registry, command routing, presence tracking, Redis cross-instance relay, and a did:web service document. Service-auth JWTs verified with @atproto/xrpc-server + @atproto/identity. - web: device picker (navbar) + bottom "Playing on …" banner, transport routing to the selected remote, transfer-here/there, and WS-driven deletion of the actor.status record when no player is online. - cli: remote module (tokio-tungstenite) making the TUI both controllable and a controller, a device-picker overlay + text indicator, a headless `--no-tui` daemon mode, and a settings.toml-configurable device name. - tests: hub integration tests (ws) + web routing/transfer + device helper tests; new GitHub Actions workflow runs web + api suites. - i18n: new `connect` namespace for en/fr/pt.

20 hours ago

feat: atradio Connect — cross-device remote control Spotify-Connect-style remote control across web + CLI. Every logged-in client opens a WebSocket to a new hub in apps/api, is grouped by account DID (verified via atproto service-auth JWT), and can list and control the other devices on the account. - api: WebSocket Connect hub (/connect) with per-DID device registry, command routing, presence tracking, Redis cross-instance relay, and a did:web service document. Service-auth JWTs verified with @atproto/xrpc-server + @atproto/identity. - web: device picker (navbar) + bottom "Playing on …" banner, transport routing to the selected remote, transfer-here/there, and WS-driven deletion of the actor.status record when no player is online. - cli: remote module (tokio-tungstenite) making the TUI both controllable and a controller, a device-picker overlay + text indicator, a headless `--no-tui` daemon mode, and a settings.toml-configurable device name. - tests: hub integration tests (ws) + web routing/transfer + device helper tests; new GitHub Actions workflow runs web + api suites. - i18n: new `connect` namespace for en/fr/pt.

20 hours ago