-
Notifications
You must be signed in to change notification settings - Fork 72
Description
Description
I find myself setting the view limit to 3 or more, even when the secret is meant for a single person, because apparently people tend to check out the secret, but trust to be able to "process" it at a later time.
However annoying this is, it's even more annoying that the secret stays "available" after the data was indeed processed by the intended viewer.
I was looking at https://github.com/pglombardo/PasswordPusher and they sort of resolve this by giving the viewer a Delete this secret link now
button.
I think that's a very good addition, because it solves the situation that I either have to remove the secret myself (if I was logged in while creating it) or have to view the secret repeatedly until its limit is reached (either as a viewer or as sender when I got the confirmation that the data was processed).
Screenshots
No response
Additional information
No response