WasNowForward Publisher

Help

Support, revocation, and deletion

Use these procedures for OAuth authorization help, failed uploads, revocation, and deletion requests.

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;
  • client_secret.json;
  • youtube-token.json;
  • access tokens, refresh tokens, API keys, private keys, or Cloudflare credentials.

Safe diagnostic information includes the command name, sanitized error text, UTC timestamp, application version, and whether the upload reached YouTube Studio.

Revoke Google authorization

  1. Open Google Account permissions.
  2. Select the connection for WasNowForward Publisher or the corresponding OAuth application name.
  3. Remove access and confirm revocation.
  4. On the authorized local computer, delete the local token file:
rm -f "$HOME/.config/wasnowforward-binaural/youtube-token.json"

Deleting this file removes the local authorization token. It does not delete the OAuth client configuration and does not delete videos stored by YouTube.

Implementation status: the currently installed engine uses Google Account revocation plus local token deletion. A programmatic in-application revocation command and authorized-data cleanup are required before the public automation audit is submitted.

Request deletion of retained application data

Email wasnowforward@gmail.com with the subject “WasNowForward Publisher data deletion request.” Identify the local installation or audit record involved without sending credentials. Authorized API data under the application's control will be deleted as soon as reasonably possible and within the applicable YouTube API policy period.

Deletion from this application does not delete data stored by YouTube. Manage YouTube-hosted videos and channel data through YouTube Studio or another authorized YouTube client.

Failed or interrupted upload

  • Do not immediately repeat a command after the media upload may have completed.
  • Check YouTube Studio for a newly created private video and note its upload time.
  • Confirm that the authenticated channel matches the expected channel.
  • Preserve sanitized terminal output, but remove credentials before sharing it.
  • Do not re-upload a video solely because thumbnail setting failed; doing so can create a duplicate.

OAuth authorization help

The publisher uses an installed desktop OAuth flow. Authorization opens in the system browser and returns through a temporary localhost listener on the operator's computer. This public site does not receive OAuth callbacks.

If authorization resolves to the wrong YouTube channel, delete the local token file, start authorization again, and select the Google or YouTube identity that owns the configured destination channel.