To truly democratize Nostr, it must function effectively on low-speed internet connections and low-end devices. The clients should remain lightweight and not become an all-encompassing "super app."
I know we all desire the convenience of having all features in one place, it is not beneficial in the long run.
Clients should genuinely explore the possibility of supporting third-party plugins and micro services integration imo 🤔
Agree. A lot of work being duplicated across clients.
Exactly, no single client can excel at every aspect, and they are also failing to leverage the microservice ecosystem built around Nostr. 🤷♂️
This! I say make a good plug-in infrastructure and also solve all the app stores’ restrictions. It should be Nostr browser! 🐶🐾🫡
💯
K.I.S.S. = Keep It Simple Stupid
Agree 1000 percent
Must function on devices primarily using wifi since mobile operating systems compromised
The beauty of a protocol like nostr is all kind of apps can browse the "nostrnet". A big heavy do-it-all apps and also lighweight low bandwith optimized ones. At this point the most attention is given to the former (as far as I can tell) because it is all new and people want to try stuff.
That said I think that a ligh nostr browser is very important.
With bad internet, Damus (for example) is a terrible experience. You have no idea if anything is loading while staring on blank screen or missing replies. So it is hard to know if you're just waiting for notes to load or there is nothing to load.
Would a manual pull - push work in extreme cases? Sort of like a offline mode, where you download a specific note structure, reply to everything offline and then push (broadcast) it once you are online? Dunno.
Could zapping become a plug-in that can be added onto Damus and other apps so none of their core features violate the App Store guidelines?
💯 (😱)
"The clients should remain *lightweight* and not become an all-encompassing "super app."
Thank you!! 🫂🤍
