You raise some great usecases. We have an option to require a password to view the secret but that doesn't directly solve the cases you bring up.
We're considering changing the basic UX to require a click to display the secret (the click will send a POST to retreive the contents). That will include a much more visible disclaimer that it's only available one time.
Comments
You raise some great usecases. We have an option to require a password to view the secret but that doesn't directly solve the cases you bring up.
We're considering changing the basic UX to require a click to display the secret (the click will send a POST to retreive the contents). That will include a much more visible disclaimer that it's only available one time.
Using a POST seems like a solid workaround. It might even be possible to include a POST form from your default email notification.