nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcscpyug would that be something you'd like to implement for zaps?
Yeah, I am thinking a lot about it. Maybe some form of zap outbox that the app keep retrying if it fails while also building a list of outgoing zaps the user can see if succeeded or failed.
I am just too afraid of retrying stuff automatically. Maybe if it fails it just marks as such and allow users to retry manually.. it's less interesting, but safer.
Yes, autoretry should be avoided, or it will open a door to hacks and abuse
I think your instincts are right on. An automatic process has the potential to go haywire. Providing an opportunity to manually retry is, I think, the smarter solution.
Maybe retry just once after a fixed amount of seconds. If it still fails, send to the zap outbox for the user to retry manually
