The issue

When browsing the site from the mobile device, it is easy to accidentally zap because we use the fingers to scroll or zoom. It has happened to me more than once. And also, when enabling the turbozap feature, it happens sometimes that the user accidentally double clicks and it zaps more than you wanted to zap. This is specially dangerous if you triple click but that is less common. Double clicks happen for sure.

Possible solution

Add the ability for the user to undo latest zap or be able to cancel zaps within a specific period of time. 20 seconds for example.

How?

Instead of zapping immediately, the system could just queue the zaps into a database where the system checks and zaps them for real if the time has passed. Then they are removed from the queue. During that time while the zap is in the queue, the user can cancel that zap and it is removed from the queue as if it never happened.

From the user perspective, the zap button and animation happens identically. But you can hold the zap button and find an additional cancel zap button in the window where you can zap custom amounts. If the time has passed, then the button is disabled or not shown.

it is just an idea but maybe there are better ways to do it, just discuss in the comments. It may seem easy as a concept but implementing it safely could be a lot of work so just ignore this feature if that is the case. :)

Cheers!

view all related items

389 sats \ 2 replies \ @OneOneSeven 17 Jan

Especially annoying when disagreeing with someone and accidently zapping them lol.

But I'm against this, I'll eat the losses, it reminds me a little of the responsibility involved with bitcoin. Sure maybe the icon could move, or add a toggleable "confirm" option for zapping on mobile/PWA or something.

But doesn't the zap go directly to the other user's wallet? What happens when they zap a post before you ask for the refund?

85 sats \ 1 reply \ @quark OP 17 Jan freebie

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.

174 sats \ 1 reply \ @siggy47 17 Jan

I feel like the turbo zaps work very well as is. I am clumsy as hell while typing on my phone, but I have no trouble with the turbo feature. On the other hand, I have zapped posts that I regretted zapping after realizing it was a bot. I have also accidentally zapped. An undo would be nice, but not critical.

0 sats \ 0 replies \ @quark OP 17 Jan

Yes I think accidental zaps happen more by trying to scroll or zoom in the phone than turbozaps. There are a lot of bots out there. Be careful with the zaps hehe. Maybe 20 seconds is not enough in that case.