GREAT QUESTION!
We’ve got so much stuff in the pipeline it’s crazy. Short answer, yes it’s going to be possible to use your nsec on other clients.
Long answer;
The ZBD client is not complete yet, but we never said it was ;) we’re building in public so we can gauge the interest of certain features that our users actually want to use.
With that said, developing a nostr client that is user friendly doesn’t happen in a day.
We are prioritizing features that our users want (like better DMs, better discovery, debugging, etc) and thoughtfully building out a UI and UX for our users to really feel comfortable using a private key.
A lot of people don’t know how to do that - it’s not intuitive and a bit scary. So we want to make sure that our users’ experience is not scary but fun and empowering.
We’re moving at the speed of light to make a friendly nostr client. We love every other client out there and want our users to feel comfortable venturing out into the nostr verse with ease. But right now, it’s a bit tricky to introduce already this new concept of social media AND THEN the concept of having to hold this weird password that will only appear once blah blah. One step at a time.
I feel like there’s a lot of blind idealism floating around and I’m here to say this: nostr is about optionality. We’re going to give our users the option to use anything that runs on nostr, but we cannot just randomly do it: we need to do it the right way.
theoriginalbhd / Brianna HD
npub1ak…mfxa8
2023-08-08 22:49:52
in reply to nevent1q…kqju
Author Public Key
npub1akngghxzy6d75y8szp6y44u5pxktwy5aj6zh6jl3ncp8d93fj2fq5mfxa8Published at
2023-08-08 22:49:52Event JSON
{
"id": "ffc0b8e30f49aad627e4524b999b1f51f2cf4e12e5562b53468258c616c23d82",
"pubkey": "eda6845cc2269bea10f010744ad79409acb7129d96857d4bf19e027696299292",
"created_at": 1691527792,
"kind": 1,
"tags": [
[
"e",
"20de0dd583205e5fb83d4d4e44633ac753ac7b058a5482c21a7c47080f94451f"
],
[
"p",
"1b11ed41e815234599a52050a6a40c79bdd3bfa3d65e5d4a2c8d626698835d6d"
],
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
],
[
"p",
"3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24"
]
],
"content": "GREAT QUESTION! \n\nWe’ve got so much stuff in the pipeline it’s crazy. Short answer, yes it’s going to be possible to use your nsec on other clients. \n\nLong answer;\n\nThe ZBD client is not complete yet, but we never said it was ;) we’re building in public so we can gauge the interest of certain features that our users actually want to use. \n\nWith that said, developing a nostr client that is user friendly doesn’t happen in a day. \n\nWe are prioritizing features that our users want (like better DMs, better discovery, debugging, etc) and thoughtfully building out a UI and UX for our users to really feel comfortable using a private key.\n\nA lot of people don’t know how to do that - it’s not intuitive and a bit scary. So we want to make sure that our users’ experience is not scary but fun and empowering. \n\nWe’re moving at the speed of light to make a friendly nostr client. We love every other client out there and want our users to feel comfortable venturing out into the nostr verse with ease. But right now, it’s a bit tricky to introduce already this new concept of social media AND THEN the concept of having to hold this weird password that will only appear once blah blah. One step at a time.\n\nI feel like there’s a lot of blind idealism floating around and I’m here to say this: nostr is about optionality. We’re going to give our users the option to use anything that runs on nostr, but we cannot just randomly do it: we need to do it the right way.",
"sig": "b9a9187d44b6376798c413173c899231c7293f99ce5c5c4b56984057bb1ef7619937758aae23a5e234f87434d96cdb0171c908557dff834ddf9f099511184963"
}