Yes!
I'm not a dev and so I might be naive on the feasabilty of the verification. But it's the best trade of I can come up with for now. It works cross-platform and has way better trade offs than bunkers etc...
Ghosting someone =. Abruptly cutting of contact with someone.
Depends on your audience, but I would not use that.
Too bad, cause it sounds cool.
Good Imposter detection + removal goes a long way.
(will probably some kind of timestamp yes)
No way that I'm showing anything more than Display Name + Following/Not icon on 95% of screens.
Colours are useful:
- to find yourself
- to find someone new
(I'm pippelina. Pink pippelina 😎)
- for imposter detection services
(If pfp, bio, last digits of npub, color, ... match with an earlier created profile)
The whole point of a follow is that you don't have to remember anything about them.
That's why you literally bookmark them.
Yes, I know. Every app can fake everything.
That's why I think a verification button that opens the same data set somewhere else (that you already know) in the onboarding process is a good solution.
It beats blindly trusting the app or centralizing "Nostr login" to a few honeypot services.
A newcomer that is only part of Nostr group chat and then opens his first new app can do a loooot more with trusting the app he already knows and the Web of Verification that that app has, than with trusting who the other chat members are following.
Follow lists will not be high signal.
A follow doesn't have a cost, it's binary and will more and more just start to mean something like "this npub is not spam and I would like to quickly retrieve it's profile info".
Trust, Verification, What and who you see in social feeds, etc... will not be based on follow lists.
Communities, Zaps, Paid services, Actual profile interaction, ... are all better bets I think.
If this dev verified those apps, why would "following" those apps prove that? Why wouldn't he prefer to sign a specific verification events?
Following nostr:npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q latest idea, one could have a subsection of an app offering a "browse this part as another user" - based on the Find Me UX
Yup, so excited to explore the UX on these new things man!
You can never "Log In" and just switch lenses all the time.
Keys are so cool.
Yes! Lying needs to be expensive.
(Never heard of the merchants of Corinth theory btw. Any good resources?)
It makes them less interoperable.
It's bad UX not to have verifiers.
It's bad marketing.
I don't mind anyone considering them anything. It's a losing strategy on an open protocol.
Maybe a “⚠️warning: closed source ⚠️” label.
The source code cannot be audited, or verified. By using this app you sign up to a greater risk of rugpull, and uncertainty in what happens with your data.
cc nostr:npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q
Can you display it as "Unsigned" and "Unverified"? Although technically you signed it, mmmm.
Maybe sign it with a "Google Playstore"-npub lol 😂 and display it as unverified and with "install at own risk"?
1. By default, I'd priotize opening that page in a native app the user already has or a web-based app he has some link with (zapped it, known app in his network, etc etc...)
2. By selecting who you are first, the app adapts the Verifiers it shows to your npub
3. I'm including Verifiers in my onboarding flow so that an onboarded user has an initial set of Verifiers (preferably independent from the app) like he would have initial Relays, Blossom servers or Mints.
Yup!
Cleaning up garbage on a landfill isn't going anywhere.
I would not have known who fiatjaf was if, like all other BS that's written on the web, this was just ignored.
Collectively hating on someone like that, just makes it easier for them to write more articles on how awful she thinks you are. Why start a feedback-loop like that?
All it takes for evil to triumph is for good people to waste time on reactive stuff like this.
Hell, even writing this here feels silly in that light. #optout #build
1. Focus 💯 on keys
2. Start with group chat invite
3. Send ecash