ClipEngine · account wiring · SU day

Get the accounts posting

One credential dance per platform. TikTok's already wired — the YouTube grant below is the repeatable one you'll run three times, once per channel. I handle everything after you hand me the token.

TikTok · @Tried.that
Creds wired Postiz healthy
YouTube · 3 channels
Your move grant needed

TikTok — the last 2 clicks

Production app creds are already in Postiz. You just authorize the account.

  1. Open Postiz
    Browser → http://192.168.1.236:5000 (on your tailnet).
  2. Add channel → TikTok → Authorize
    Because you're already signed into @Tried.that in that browser, there's no login — just the consent screen. Approve all 6 permissions.
That's it for TikTok. Unaudited = posts go out private (SELF_ONLY) immediately — plenty for SU. Public flips on automatically when the audit clears. Tell me once it's connected and I'll run a dry-run post.

YouTube — run this 3× (once per channel)

You've made the OAuth client for zionboggan@gmail.com. This grant turns it into a durable token. Same steps for each channel — you just pick a different channel on the consent screen each time.

  1. Install the one library
    On a machine with a browser (your computer is easiest):
    pip install google-auth-oauthlib
  2. Put the script + your client-secret in one folder
    The script is on the share at P:\ClipEngine\yt-creds\yt_oauth_grant.py. Drop your downloaded client_secret_…json next to it.
  3. Run the grant
    python yt_oauth_grant.py client_secret_170058961467-…apps.googleusercontent.com.json
    A browser window opens automatically.
  4. Approve in the browser
    Sign in as zionboggan@gmail.com → on the "unverified app" screen click AdvancedGo to (continue)pick the channel you're wiring (Clip Radar or Clip Vault) → approve the youtube.upload permission.
  5. Confirm the token
    It writes yt_token.json and prints refresh_token present: True. That "True" is the thing to check.
  6. Hand it to me
    Drop both yt_token.json + the client_secret_…json into P:\ClipEngine\yt-creds\ and tell me which channel you picked. I wire it into config.json on the 3060 and run a dry-run upload — no more input from you.
One gotcha that saves a redo: the OAuth client must be type "Desktop app" (localhost redirect just works). If you built a "Web application" one, either recreate it as Desktop app, or add http://localhost to its authorized redirect URIs.

The three YouTube channels you're wiring:

ChannelConfig slotGoogle acct
Clip Radar · Yaya Bogganyt_yaya_bogganzionboggan@
Clip Vault · Euphoria Softwareyt_euphoria_softwarezionboggan@
Daily Clip Drop · Zion Bogganyt_zion_bogganzionboggan0@
Clip Radar & Clip Vault share the zionboggan@ account (pick the right channel on the consent screen). Daily Clip Drop is the separate zionboggan0@ account — different login.

What I'm handling in the background

So you only touch what genuinely needs a human.

  1. TikTok production creds wired into Postiz
    Container recreated, healthy, verified.
  2. Watchlist SU-ready
    25 channels, squatters purged, priority students added, validated.
  3. → Every token you hand me
    Placed on the 3060, wired into config, dry-run tested — before anything's enabled.
  4. → Fable's SU tooling
    Getting the production panel + edit-pane wins integrated next.