β dumb relay, smart client
β smart relay, dumb client
β
smart relay, smart client
Login to reply
Replies (12)
ima make
π retarded relay, based client
What about
Retarded relay, retarded client?
π€
What is wrong with dumb relay, smart client? Isn't that the essence of Nostr?
an essence so good that 99.9% of people don't stick around πΈ
I thought about that
But you canβt just go full retard


β
your relay, your client
I mean you can..
But you shouldnβt..
But you can..
80 IQ π

Even if you improve user retention you will have users bind to a smart relay, essentially a silo... Or is there something I'm missing and you will be able to preserve things like censorship resistance?
π§ dumb relay, dumb client. Write the JSON yourself.
Should we promote share as the primary way to onboard users from the web? It seems like the most effective tool to replace manual copy-pasting, making the transition from a browser to a Nostr client seamless for new users.
Iβm building a project right now and hit this exact wall. Itβs easy to fix. Iβve just drafted a solution and shared it as NIP-222 on GitHub:
This would be a massive win for your client and the ecosystem as a whole. Take a look, would love to hear your thoughts on pushing this forward.
GitHub
Draft: NIP-222 - URI Scheme for Share Intents by Ty13rS2 Β· Pull Request #2266 Β· nostr-protocol/nips
Mobile UX for sharing into Nostr is broken. This draft proposes a standardized intent URI (nostr:share?text=...) to allow external web apps and gam...