Support, authorization, revocation, and recovery

Contact support

Email wasnowforward@gmail.com and include “WasNowForward Publisher” in the subject line. Messages are reviewed on a reasonable-efforts basis; no fixed response time is promised.

Never attach or paste Google passwords, OAuth client-secret JSON, access tokens, refresh tokens, API keys, private keys, keyring exports, or Cloudflare credentials.

Safe diagnostic information includes the command name, sanitized error text, UTC timestamp, Publisher version, receipt path, and whether a private video is visible in YouTube Studio. Do not paste the receipt before checking that it contains no unrelated private metadata.

Accept the current policy and authorize the channel

Review the exact policy identity shown by the installed application, then record acceptance:

wnf-publisher legal show
wnf-publisher legal accept --accept

Authorize the existing Desktop OAuth client and bind the exact expected channel:

wnf-publisher auth authorize \
  --client-secrets /absolute/path/to/client_secret.json \
  --expected-channel-id UCig0gVZkrj8Db9-SGpCZQKg

The browser returns to a temporary localhost callback. This public site does not receive OAuth callbacks. Publisher refuses the operation if the actual granted scopes or authenticated channel do not match the approved configuration.

Check authorization safely

wnf-publisher auth status \
  --client-secrets /absolute/path/to/client_secret.json

wnf-publisher auth check \
  --client-secrets /absolute/path/to/client_secret.json \
  --expected-channel-id UCig0gVZkrj8Db9-SGpCZQKg

auth status reads secure local metadata. auth check can refresh authorization and contact YouTube to verify the exact channel, so use it only inside an authorized live-acceptance or operating window.

Revoke Google authorization and purge matching local API data

Use the confirmed RC1 command:

wnf-publisher auth revoke \
  --client-secrets /absolute/path/to/client_secret.json \
  --confirm-revoke

The command records a durable intent, revokes the provider grant, deactivates the exact local authorization, and purges matching profile-bound authorized API receipts and cache data. It does not delete operator media or videos stored by YouTube. Inactive immutable credential versions may remain in the OS keyring and are not selected for active use.

Access can also be removed through Google Account permissions, but external revocation does not by itself complete Publisher's local cleanup.

Legacy token-file warning

RC1 does not use youtube-token.json as its active credential store. Do not manually delete or copy a legacy token file as a substitute for RC1 revocation. When an approved legacy migration is required, use the application's auth migrate-legacy procedure with the exact client and profile, or obtain support before proceeding.

Failed, interrupted, or uncertain private upload

• Do not create a new preset, change the selected media, or use a duplicate override merely because terminal output was interrupted.
• Check YouTube Studio for a newly created private video and note its upload time and video ID.
• Preserve the local upload receipt and publication claim. They bind the exact video, thumbnail, metadata, client/profile, and destination channel.
• Use the same exact release inputs to resume a partial thumbnail or processing check. Publisher is designed to resume the existing provider object or prevent an accidental duplicate.
• Never use --allow-duplicate-upload during the bounded RC1 private smoke test.
• Preserve sanitized terminal output, but never share credentials or secret-bearing keyring data.

Request deletion of retained application data

Email wasnowforward@gmail.com with the subject “WasNowForward Publisher data deletion request.” Identify the installation, profile, or receipt involved without sending credentials.

Deletion from Publisher does not delete data stored by YouTube. Manage YouTube-hosted videos and channel data through YouTube Studio or another authorized YouTube client that supports the requested action.