Beware of the NINO:
Nostr in name only
(Name by @fiatjaf ) nostr:note19626gszwymsnn234383qr4y5h24e6ly3kac767jvzru3w8nglnls77sg75
Beware of the NINO:
Nostr in name only
(Name by @fiatjaf ) nostr:note19626gszwymsnn234383qr4y5h24e6ly3kac767jvzru3w8nglnls77sg75
Thank you for the heads up!
Quick thought on this, if websites start implementing "login via nostr", it would be a good idea to have a separate nsec that you don't use for much that you could plug into those things. They'll be useful, same as "login via Google" is useful, but it's important to have shields up. Maybe nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm could preempt this by setting up a way to create a profile/keypair specifically for that purpose where the system can make sure that there is a clear separation between our various profiles and outside services have a harder time breaking down walls without permission.
Personally, I would be very happy if nostr became an alternative to logging in with a Google account or Email.
I was accused of starting a NINO when I first put up nostrspaces.com but now we have nostr native nostrnests.com. Even if they start with a simple integration I'd expect more integration over time.
Then DINO would be "Decentralized In Name Only" π