nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr - I think this would be awesome for nostrudel.ninja as well, something to consider, cheers!

nostr:nevent1qqspd60e5755hvs35wqvl9ga3kzlt2gk96ltafj37q0nypvhft04w6qpvemhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0dec82c330fnrj63cw45xkae5xfcnjvnwvdax5cmrw3h8svm3v45x6dmjw5mnjerv89mxgdtjvvmhqcttw94rjapewfehx7n3x5mxs0mzwfhkzerrv9ehg0t5wf6k2qguwaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skc5tpq75

Reply to this note

Please Login to reply.

Discussion

It dose sound appealing. although I think it introduces a lot of complexity into the zapping process. right now when you zap a note you only pay one person (plus a few more with splits) but if every zap got split three ways thats three times the complexity and three times the chance for something to break. not to mention it would be really hard to explain to the user whats going on

Zap pool?

I don't know what a zap pool is, but if it involves the user paying multiple lightning invoices then its too complicated to work more than once

Mmm ya i could see that being rough now that you mention it, and would make user experience pretty clunky if you just zapping casually and run into several users in a row with splits defaulted. Thanks for hearing me out, friend. Im loving nostrudel.ninja 🤙