Sign up flow + Main actions for Nsec.app #nostrdesign
https://cdn.satellite.earth/e4c8892581da7d57bcccbe060446692e9a299961a7be8e864bdec4b82a2e9c53.mov
nostr:npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxy nostr:npub1zfss807aer0j26mwp2la0ume0jqde3823rmu97ra6sgyyg956e0s6xw445 what do you think? I personally really enjoy the flow with the slide-up drawers like this + the invitation for app discovery. Next:
- Section for basic and advanced actions in Settings
- Maybe some screens to edit profile (pic, name, etc)
- A logo
Figma: https://w3.do/aZ3OUJ_v
We’re on the same wavelength.
Directing newcomers to THE SAME celebrity follows only centralizes and weakens the nostr “signal”.
We need onboarding tool(s) for advocates to invite their own friends and grow their own social networks.
Like this:
nostr:note1are6y6755gu06300epxkcvj7w9mksffm2tkzhs7se0j0u5qhfpxspzsssj
nostr:note1e9mxgp6qc6tgt4j8pdd5dc7drrutqrgml4vnqty9d78vw0hkcq4sqe6cgg
I clear caches regularly. 🤷🏻♂️
It adds the label if both the following is true:
- you are not following the contact
- it has a 80% similar name and profile picture as someone you already follow
For picture it checks pixels and for name it uses Jaro-Winkler from https://github.com/autozimu/StringMetric.swift I tried levenshtein before but it seemed a bit buggy. Both could probably be improved but I haven't had false positives for a while, there were a few a while back but that was actually related to code errors, not the algorithms.
Thanks. Do you think “in code” wd be better than “in person” for verification of the same data points?
IMHO a crowdsourced solution (allowing people to “verify” each others names and pfp) allows erroneous claims (from a single person) to be ironed out by the claims from others. I imagine this wd be easier to implement and to maintain and produce better results than an algo (a black box for many) locked in code.
Your thoughts?
(ICYMI that screenshot above is a false positive.)
Exactly I’m working on THIS onboarding app with built in DM to support advocates sharing nostr with friends:
nostr:note1n56dpv3ck393nz9axmf5j9esnyaj642sfawqne4zs9ufy9865cvqu056gx
#nostr has been refreshingly #welcome since my #firstpost
Happy Holidays #everyone
nostr:note1hdu2qljaa2dpwlvnvh46tjyk9az3lawt6lxchl2xsnrrcvrlpejsh5yc2h
Timeless
nostr:note1szjrddrgxe8d9y32hvmx36k5aty2423gw8h4322mmzu45dzct2ksx6mj0a
nostrmeet.me 👉 onboard an entire team, club, family, ect… all at once, with a custom invite code linked to a private group chat.
nostr:note1n56dpv3ck393nz9axmf5j9esnyaj642sfawqne4zs9ufy9865cvqu056gx

DM right in the onboarding client.
nostr:note1n56dpv3ck393nz9axmf5j9esnyaj642sfawqne4zs9ufy9865cvqu056gx
This is the way. 👇🏼
nostr:note1llrjhvgnzuqf97hv5y6v0np2lzr4awc8u0am3u57nzzy7h4pflzs3kzw8v
Just pretend. Works every time.
Forget 2 week summit. Just get all the client devs on a conference call and make them talk about it.
For an hour?
No… three hours. That should do it.
It is getting better.
#nostrux #grownostr
nostr:note1xec90qlgmc658thnnqngtrs4w58kvfd7f95fuvhg5a8axwg9l5ssgr6ap9
You’re both right. 🙄
UX is a shambles across the board.
AND end user configuration of relays (instantiating, subscribing, and posting) WILL BE what differentiates nostr from AP (where you only get one server) and what brings the masses.
What is govt mandated oversight?
nostr:note1dsdyz5hlu7hhf50zlaysz4shufzpu6l9yxns6wh7ch5apdzg303sq8ny90
nostr:npub1n0stur7q092gyverzc2wfc00e8egkrdnnqq3alhv7p072u89m5es5mk6h0
Love the fact that you flag possible imposter account for users!! Seems prone to false positives tho. Wondering what variables you are checking on?
- is followed?
- similar PFP? (how do you assess?)
- similar name? (How similar?)
- what else is checked?
Because, we’re interested to implement a “code free” crowdsourced solution (set of guidelines and a NIP) for exactly this.
#nips #onboarding #verification #grownostr nostr:npub1san22nhe59ct8pstcehav4dtkf94lkn46ltl7d30g3zzl00tg7ussgqjdd

Now you getting me riled up! It’s a contagion.
