This site is locked until Supabase Auth, Telegram as a custom OIDC provider, and server-side access checks are configured. Add the public Supabase project URL and publishable key to js/supabase-config.js, then follow the setup guide. Never add the Telegram Client Secret or Supabase service-role key to this repository.
Connect your verified Telegram identity and request access to the link workspace. Conversion opens after an administrator reviews your account.
Permission is linked to Telegram’s verified account ID—not to a display name.
Approve verified Telegram accounts or revoke access. Usernames are shown for convenience; each decision is tied to a Telegram account ID.
Loading requests…
Loading accounts…
No revoked accounts.
Paste a supported Google Share address to generate its alternate URL format. Review the result, then copy it from this compact workspace.
Input check · output builder
The source address is sent to the protected conversion service to verify permissions. This workspace does not add tracking analytics.
Only a verified account with active permission can use this workspace.
The service checks the account status again for every conversion.
Administrators can pause or restore access from the control panel.