Go Live gated on auth; scene building stays auth-free; update design docs
This commit is contained in:
@@ -13,11 +13,11 @@
|
||||
|
||||
---
|
||||
|
||||
## TASK 2 — YouTube OAuth2 Authentication (optional, non-blocking)
|
||||
## TASK 2 — YouTube OAuth2 Authentication
|
||||
|
||||
**Goal:** Fully working Google OAuth2 flow — user clicks "YouTube", browser opens, authorization callback lands, channel info is stored.
|
||||
|
||||
**Design constraint:** Sign-in must NEVER block core usage. Users can go live with a manual stream key, build scenes, and record without authenticating. OAuth is an enhancement — it unlocks live chat, broadcast creation, scheduling, and YouTube-side health — not a prerequisite.
|
||||
**Design constraint:** Sign-in must NEVER block core exploration. Users can build scenes, add sources, and audition the software without authenticating. But **going live requires authentication** — "Go Live" only appears once connected. OAuth is what unlocks the actual broadcast (plus live chat, scheduling, and YouTube-side health).
|
||||
|
||||
### Requirements:
|
||||
|
||||
@@ -26,7 +26,7 @@
|
||||
3. **Browser launch** — open the authorization URL in the default browser
|
||||
4. **Token persistence** — store access/refresh tokens securely (Windows DPAPI), reload on startup
|
||||
5. **UI state** — account name/avatar shown when connected; "sign in (optional)" affordance, never a gate
|
||||
6. **Stream key entry stays manual** — OAuth does not replace the manual stream key path
|
||||
6. **Go Live gated on auth** — "Go Live" button only visible once authenticated; scene building works without it
|
||||
|
||||
### Tests:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user