jonb on Nostr: I've been continuing to mull over the sign-in flow for Nostr apps. It seems more ...
I've been continuing to mull over the sign-in flow for Nostr apps. It seems more complex than the legacy system because of the need to account for more than one method of authentication: extension, public/private keys, nostr connect.
Even if one method becomes standard in the future, I think there's still a question of how to accommodate users who continue using older methods. Examples and more thoughts in thread 🧵. cc
Karnage (npub1r0r…q9ac) /
nostrdesign (npub1x6g…rtxj) Tags: #ux #design
Published at
2023-07-16 06:35:20Event JSON
{
"id": "bb4bf7b25d022b90ecf3af27314b9032500d38266a91115f3fbd6607363af134",
"pubkey": "35a8f9c0272c119a620f47c055c8db39e9f805fef1b22d0b7a42b189351dae66",
"created_at": 1689489320,
"kind": 1,
"tags": [
[
"p",
"1bc70a0148b3f316da33fe3c89f23e3e71ac4ff998027ec712b905cd24f6a411"
],
[
"p",
"369061c9a1ee258d28d123f35f913968884d52c4928ab7bd5a4544fcfd48f3f3"
],
[
"t",
"ux"
],
[
"t",
"design"
]
],
"content": "I've been continuing to mull over the sign-in flow for Nostr apps. It seems more complex than the legacy system because of the need to account for more than one method of authentication: extension, public/private keys, nostr connect.\n\nhttps://void.cat/d/YFiXaAVnb54ifi9FKmtsui.webp\nEven if one method becomes standard in the future, I think there's still a question of how to accommodate users who continue using older methods. Examples and more thoughts in thread 🧵. cc nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac / nostr:npub1x6gxrjdpacjc62x3y0e4lyfedzyy65kyj29t0026g4z0el2g70esc0rtxj \n\nTags: #ux #design",
"sig": "67c32da7e881ccb85048819038968a96f059929c4d57c9134472ef28d2c47535fcc15d11a78685dc5427d837cb0a60e4df1ef51227ca28362207b8e34e58bc8f"
}
