SUPPORT

When a view doesn’t load.

ViewsMeet has no account recovery flow. Most issues are temporary service errors, expired private links, connectivity, or a control token stored on another browser.

Today’s five will not load.

Check connectivity

An offline badge means the current screen can be read but new picks cannot be submitted.

Retry once

Use the retry button. Repeated rapid retries can trigger a protective rate limit.

Use the labeled demo

Add ?demo=1 to inspect interface behavior. Demo values are visibly labeled and are never live counts.

Keep a request ID

If an error displays a request ID, preserve it when reporting the problem through the channel that provided this deployment.

A friend link is unavailable.

It may be mistyped, deleted by its creator, or expired. Private links deliberately do not appear in search results. Ask the creator for a new link or make today’s challenge your own.

A private challenge is being misused.

Open “Report this challenge” on its landing card and choose a fixed safety reason. Reports contain no free-text message and do not expose your identity to the challenge creator. Repeated reports from the same coarse network are deduplicated.

For immediate danger, contact the appropriate local emergency or platform service; ViewsMeet is not an emergency channel.

I cannot see delete controls.

Creator and response controls rely on opaque tokens stored in the browser that created or submitted the challenge. They do not follow you to another browser or device. Clearing site storage removes local access to those controls.

Never send a management URL or token to someone else; possession grants its limited control.

Keyboard, motion, and screen readers.

All game choices are native buttons and can be reached with Tab, activated with Enter or Space, and reviewed with the Back control. Status changes are announced through a polite live region. The interface follows reduced-motion and increased-contrast preferences.

If focus appears lost after a transition, press Tab once; the active question and controls remain in document order.

Machine clients.

Inspect OpenAPI for current field requirements and use the links on the Agents screen. Treat 429 as a retry-later response. Preserve error code and optional request ID. Never silently substitute demo data for a failed live response.