I would imagine with just an nsec, they can't do proper key derivation (like they can with seed phrases)
So just having an nsec means their messaging scheme couldn't function. Just a guess though.
Discussion
Indeed. It is probably worth the trouble of supporting legacy nsec identities to get users in the door
And then write a sweet migration tool that automatically notifies your compatriots once you migrate to a proper seed phrase
If I understand correctly, you want Keychat to support importing nsec, which would increase the complexity of Keychat. We will consider this issue once Keychat reaches a stable version. We recommend not using the same ID for Damus and Keychat.
You must consider the cost of forcing new identities on potential users, identities that are an anti feature to most current nostr users
Am I on an older version? Because when I go to "Create ID", I have the option of "From seed phrase" and "From nsec".
Upgraded to 1.31.13 and still seeing the Import from nsec option.
I misunderstood you. The current version does support nsec, but we still think seed phrases are better.
> When you say that seed pharse If I understand correctly, you want Keychat to support importing nsec, which would increase the complexity of Keychat. We will consider this issue once Keychat reaches a stable version.
I'm a bit confused, when you talk about supporting nsec import in a future version, is that in a different context? Like an onboarding flow? (Since the current version supports nsec import at ID creation stage)
The version that only supported seed phrases was released about 10 months ago. We received a lot of feedback requesting nsec support, so around 8 ？months ago, we added nsec support.
Ah, I didn't read the date on those quoted posts, I thought they were new posts. That explains it thanks!