pull down to refresh

Did you receive the message from some guy?
Oh, just saw your reply
100 sats \ 3 replies \ @siggy47 6h
I guess the big issue is the actual send/receive reliability. Nostr traditionally sucks at that, right?
reply
36 sats \ 2 replies \ @optimism 5h
Not entirely sure what you mean, but if you mean discovery, it depends on your relay. The most popular relays can be slow sometimes, and I figured that this is why when I open Amethyst it takes up to 3-4 minutes sometimes to load everything up.
One of the things I think is needed w/ nostr is "offline-first", like email. I'd want to have a local cache of everything I've already seen; especially my own notes, and keep track of what got published where, republish when needed. This may feel antithetical to some nostr (pwa) dev patterns but local state should always trump relay state, even if you run your own relay.
reply
100 sats \ 1 reply \ @siggy47 5h
All I meant was the nostr dms seem unreliable. I assume it's usually a relay thing. I like your idea of a local cache. A non tech guy like me just wants the thing to work.
reply
169 sats \ 0 replies \ @optimism 5h
Designing for reliability is a bit of an art, and it's hard. It took Signal something like 4 months with at least half their dev team to finally deliver their backup feature in all its glory (and I must have seen every line of code, including the ones they reversed, lol) and these aren't noobs. So let's see what's what. If it's not reliable, maybe it can be made reliable. Affero isn't the worst license to contribute under when it's FSF-assigned (which whitenoise is.)
reply