pull down to refresh

I think confirming all the time would be worse. I don't want to change the zap from the current user experience. The zap and button change happens instantly as if the zap was sent to the user but it is sent to a queue instead. The user wouldn't notice any difference when zapping. And just adds the possibility of cancelling a zap. I don't know. Maybe it is too complicated and we have to live with accidental zaps. It seems it is more common than I thought.
34 sats \ 0 replies \ @ek 18 Jan
I think a confirm button if the zap is above a threshold could be useful.
For example, anything above 1k might be unusual so opt-in confirmation could prevent accidental big zaps.
reply