Social connections, publishing & live status

CreatorOS connects creator accounts through OAuth, stores tokens encrypted at rest (AES-256-GCM, ENCRYPTION_KEY), and only requests the scopes each feature uses. A provider with blank credentials in .env is simply unavailable in the UI — nothing crashes.

How it fits together

Redirect URI for every provider: https://krunc.com/social/callback/{provider} (provider keys: twitch, youtube, discord, kick, x, facebook, instagram, tiktok, reddit, linkedin).

Background work runs from php bin/worker (cron every minute with --once, or as a daemon):

• publisher.due (60 s) — enqueues scheduled posts whose time has come (the publish job is also queued at schedule time; the scheduler is a safety net).
• social.refresh_tokens (30 min) — refreshes tokens that expire within 30 minutes; accounts whose refresh fails are marked expired and must be reconnected.
• live.poll (2 min) — checks Twitch / YouTube / KICK accounts, records live_streams, flips the creator profile live badge and fires stream.started / stream.ended automations.

Feature flags

Insert a row in feature_flags to switch a provider off without removing credentials (e.g. while waiting for app review):

INSERT INTO feature_flags (`key`, enabled, description, updated_at) VALUES ('social.instagram', 0, 'Waiting for Meta app review', UTC_TIMESTAMP());
-- later
UPDATE feature_flags SET enabled = 1 WHERE `key` = 'social.instagram';

A missing row means "enabled if credentials exist".

Per-platform status

"verify" = implemented from the official documentation but not yet exercised against a live account from this host. The provider surfaces the platform's error message verbatim if a call fails — nothing is faked as success.

Setting up each OAuth app

1. Create the app on the platform's developer portal and add the redirect URI above.
2. Put the client id/secret in .env (see .env.example) — the provider card on /dashboard/social turns from *unavailable* to *Connect*.
3. Connect from /dashboard/social as a workspace staff member or higher. The account is attached to the workspace's first creator profile.
4. For platforms that need review, keep the feature flag off until approval; you can still connect as an app tester.

Stream destinations

/dashboard/social/destinations (admin and above) stores the RTMP/RTMPS server URL + stream key for every place a creator broadcasts, so they can be copied into OBS / Streamlabs (Settings → Stream → Service *Custom…*). It is a secure address book, not a relay: video still goes from the encoder straight to each platform. Multistreaming to several destinations at once needs a multi-output plugin or a relay service.

• Stream keys are encrypted at rest (AES-256-GCM, ENCRYPTION_KEY); lists show only the last four characters. Reveal and Copy key fetch the key over an audited JSON POST (stream_destination.revealed in the audit log, last_revealed_at on the row) — the raw key is never rendered into page HTML.
• Deleting a destination is a hard delete so the encrypted key does not linger. Rotate a leaked key on the platform first, then update it here.
• Server URLs must be rtmp:// or rtmps://. Presets live in App\Modules\Social\Services\StreamPresets and come from each platform's own streaming-software instructions:

Plan limit: limits.stream_destinations on the tenant (default 12).

Publishing rules

• One post, many targets. Each target can carry its own text variant; the strictest character limit among selected accounts is shown live in the composer.
• Hard limits enforced server-side: X 280, Instagram 2200, TikTok 2200, LinkedIn 3000, YouTube 5000, Facebook 63,206, Reddit title 300.
• Media are public URLs (upload from the composer stores an image under /uploads/...). Instagram/TikTok/YouTube need media; X/LinkedIn are text-only for now.
• Scheduled times are entered in the user's timezone (users.timezone) and stored in UTC.
• Results are per platform: published, failed (with the platform's error, retry button), post status published / partial / failed.
• post.published automation trigger fires when at least one target succeeds.

Live status

/live lists profiles with is_live = 1; category chips come from config('app.live_categories'). Platform categories are mapped (e.g. "Grand Theft Auto V" → "GTA RP"). A manual override from the profile editor (live_platform = manual) is never cleared by the poller.

Future work: Twitch EventSub (stream.online / stream.offline webhooks) would replace polling for Twitch and cut latency to seconds; it needs a public HTTPS callback with signature verification (Twitch-Eventsub-Message-Signature) and app access tokens. YouTube offers PubSubHubbub for uploads but not live state.