js · streamplace · Tangled

This repository has no description

13 folders

Eli Mallon · VODs: publish livestreams as VODs automatically when opted in (port of #1330). A new autoPublishVods boolean on the place.stream.server.settings record, opt-in, with toggles in Privacy & Security and on the live dashboard for VOD-beta accounts. When the node sees a livestream record end (not a backfilled or redelivered ended record) for a streamer it serves who has it on, it queues an auto_publish_vod task: after 15s, re-checking the setting, skipping a livestream already finalized by hand, waiting up to 8x15s for recording objects still being written, it queues the existing finalize with Publish set. The upload is named after the livestream so a re-run cannot start a second VOD. A finalize meant to publish whose publish fails now leaves a ready draft. The live-VOD finalizer refuses banned accounts itself. Deleting a settings record removes its indexed copy. The livestream VOD helpers (item type, draft, synthetic upload) move into statedb, shared by the app route, the operator route and the task; SettingToggle gains disabled and aria-checked. The PR's e2e flows, go-conventions doc and leak_test change are left out: this branch has none of that scaffolding · 1w ago

VODs: publish livestreams as VODs automatically when opted in (port of #1330). A new autoPublishVods boolean on the place.stream.server.settings record, opt-in, with toggles in Privacy & Security and on the live dashboard for VOD-beta accounts. When the node sees a livestream record end (not a backfilled or redelivered ended record) for a streamer it serves who has it on, it queues an auto_publish_vod task: after 15s, re-checking the setting, skipping a livestream already finalized by hand, waiting up to 8x15s for recording objects still being written, it queues the existing finalize with Publish set. The upload is named after the livestream so a re-run cannot start a second VOD. A finalize meant to publish whose publish fails now leaves a ready draft. The live-VOD finalizer refuses banned accounts itself. Deleting a settings record removes its indexed copy. The livestream VOD helpers (item type, draft, synthetic upload) move into statedb, shared by the app route, the operator route and the task; SettingToggle gains disabled and aria-checked. The PR's e2e flows, go-conventions doc and leak_test change are left out: this branch has none of that scaffolding

Nav lockup shows the node's site title, not the brand wordmark

VODs: publish livestreams as VODs automatically when opted in (port of #1330). A new autoPublishVods boolean on the place.stream.server.settings record, opt-in, with toggles in Privacy & Security and on the live dashboard for VOD-beta accounts. When the node sees a livestream record end (not a backfilled or redelivered ended record) for a streamer it serves who has it on, it queues an auto_publish_vod task: after 15s, re-checking the setting, skipping a livestream already finalized by hand, waiting up to 8x15s for recording objects still being written, it queues the existing finalize with Publish set. The upload is named after the livestream so a re-run cannot start a second VOD. A finalize meant to publish whose publish fails now leaves a ready draft. The live-VOD finalizer refuses banned accounts itself. Deleting a settings record removes its indexed copy. The livestream VOD helpers (item type, draft, synthetic upload) move into statedb, shared by the app route, the operator route and the task; SettingToggle gains disabled and aria-checked. The PR's e2e flows, go-conventions doc and leak_test change are left out: this branch has none of that scaffolding

config-react-native-webrtc

iOS: move AVAudioSession ownership into the RTCAudioDevice fork

stream post: a running view total (playback sessions since the livestream began, kept in statedb) in grey beside the live viewer count, which goes red while live; viewerCount events carry it as total

Add white-label brand pipeline: flat dir in, all logos/icons generated

VODs: publish livestreams as VODs automatically when opted in (port of #1330). A new autoPublishVods boolean on the place.stream.server.settings record, opt-in, with toggles in Privacy & Security and on the live dashboard for VOD-beta accounts. When the node sees a livestream record end (not a backfilled or redelivered ended record) for a streamer it serves who has it on, it queues an auto_publish_vod task: after 15s, re-checking the setting, skipping a livestream already finalized by hand, waiting up to 8x15s for recording objects still being written, it queues the existing finalize with Publish set. The upload is named after the livestream so a re-run cannot start a second VOD. A finalize meant to publish whose publish fails now leaves a ready draft. The live-VOD finalizer refuses banned accounts itself. Deleting a settings record removes its indexed copy. The livestream VOD helpers (item type, draft, synthetic upload) move into statedb, shared by the app route, the operator route and the task; SettingToggle gains disabled and aria-checked. The PR's e2e flows, go-conventions doc and leak_test change are left out: this branch has none of that scaffolding

VODs: publish livestreams as VODs automatically when opted in (port of #1330). A new autoPublishVods boolean on the place.stream.server.settings record, opt-in, with toggles in Privacy & Security and on the live dashboard for VOD-beta accounts. When the node sees a livestream record end (not a backfilled or redelivered ended record) for a streamer it serves who has it on, it queues an auto_publish_vod task: after 15s, re-checking the setting, skipping a livestream already finalized by hand, waiting up to 8x15s for recording objects still being written, it queues the existing finalize with Publish set. The upload is named after the livestream so a re-run cannot start a second VOD. A finalize meant to publish whose publish fails now leaves a ready draft. The live-VOD finalizer refuses banned accounts itself. Deleting a settings record removes its indexed copy. The livestream VOD helpers (item type, draft, synthetic upload) move into statedb, shared by the app route, the operator route and the task; SettingToggle gains disabled and aria-checked. The PR's e2e flows, go-conventions doc and leak_test change are left out: this branch has none of that scaffolding

playback-router

design-system: token-based foundation, primitives, and component library

sessions: a rejected OAuth session signs the app out, and the password path is retired. A viewer signed in with the password against the PDS could open the live dashboard when the node held credentials for the account (the nodeSession bypass of Sep 23), but the dashboard's own calls to the node, starting and stopping the stream and the multistream targets, take only a node OAuth session, so every one of them answered 401 and the page sat there broken. The network's OAuth works again, so that path goes: --account-credentials and the access status's nodeSession are removed, the dashboard and the phone go-live page ask a bearer session for a node OAuth sign-in as before, and --dev-account-creds stays for development only. Separately, when the node answers a request with "oauth session revoked" or "oauth session not found", or the OAuth client gives up on a refresh, the client's tokens can still look valid and the app stayed signed in while every authenticated call failed; the agent now notices that answer once, drops the session and opens the login modal on the OAuth flow

VODs: publish livestreams as VODs automatically when opted in (port of #1330). A new autoPublishVods boolean on the place.stream.server.settings record, opt-in, with toggles in Privacy & Security and on the live dashboard for VOD-beta accounts. When the node sees a livestream record end (not a backfilled or redelivered ended record) for a streamer it serves who has it on, it queues an auto_publish_vod task: after 15s, re-checking the setting, skipping a livestream already finalized by hand, waiting up to 8x15s for recording objects still being written, it queues the existing finalize with Publish set. The upload is named after the livestream so a re-run cannot start a second VOD. A finalize meant to publish whose publish fails now leaves a ready draft. The live-VOD finalizer refuses banned accounts itself. Deleting a settings record removes its indexed copy. The livestream VOD helpers (item type, draft, synthetic upload) move into statedb, shared by the app route, the operator route and the task; SettingToggle gains disabled and aria-checked. The PR's e2e flows, go-conventions doc and leak_test change are left out: this branch has none of that scaffolding