Questions, corrections and takedowns

tokenusage.dev is operated by Pistachio Technology Inc.

Issues there are public. Never post your share token, phone number or verification code, and leave out anything you would not want anyone to read.

For anything that should not be public, email support@tokenusage.dev.

SMS reset-alert help

For verification or delivery trouble, email support@tokenusage.dev, or open an issue that says the problem concerns Reset Alerts and describes what happened. Never post your phone number or verification code in a public issue. Reply STOP to cancel texts. If you previously replied STOP, reply START before subscribing again on the Reset Alerts page.

A question or a correction

Say which page, what it says and what you think it should say, with a source if you have one. For a figure that looks wrong on a profile, give the handle and the day or month.

A takedown

Handles are self-chosen and unverified, so one can impersonate someone. To ask for a handle, a profile or a report page to come down, give its address (such as tokenusage.dev/u/<handle>) and why: whom it impersonates, or what on it should not be public.

If it is your own share, you do not need to ask: the plugin can delete it or take the report page down at once. Privacy has the commands.

A lost share token

The token from your first share is the only proof that a handle is yours, so a share without it cannot be updated or deleted from the plugin. Say which handle, and what you can about it. To start over under a new handle, run python3 scripts/share.py --forget first: it drops whatever token the plugin still holds on your machine.