Huge improvement proposal for Nostr clients - if I post something and relay connections are not very good (bad internet, relay outages, I exit the app too soon), hold the post in local storage and retry later automatically.

If the note is not seen by enough relays, keep retrying.

It happens to me quite often that I post / reply only to find out that the post is long gone and not stored on any relays.

Happened with Damus, Plebstr and Iris at least...

Reply to this note

Please Login to reply.

Discussion

I added something like this to NDK where if you publish something and it’s not successfully published to a relay it lets the developer know so they can handle it, but I should add a possibility to configure re-attempting to publish if they’ve connected a cache.

This is a really good idea

nostr:npub1tfzcrk7ly9u6e38rhl2rrm06vsgl793r9m8zf3kz78wq5qx0nnvqfqy0wj

I would add a verification option and only consider it posted when enough relays actually return the note if requested.

Ups. I expected it's working this way already.

There also should be feature to rebroadcast old posts. Sometimes I send post on some experimental client and figure out after some time it has no stats, but Plebstr see it. Or some bug in Plebstr itself.

nostr:npub1plstrz6dhu8q4fq0e4rjpxe2fxe5x87y2w6xpm70gh9qh5tt66kqkgkx8j Not necessarily in the UI, it could be done automatically when app see some of my posts is not on the all proxies.

+1