Oddbean

The current version of Keychat uses a seed phrase instead of nsec. This has caused a lot of controversy, with many people believing that Keychat does not understand the spirit of Nostr: having a single Nostr ID that is universally used across all Nostr apps. In fact, the first version of Keychat used nsec. Later, we intentionally switched to seed phrases. Why? Just like when we use Bitcoin wallets, we now more often use seed phrases rather than private keys. Using a seed phrase is an improvement in user experience. Moreover, NIP-6 defines the basic key derivation from mnemonic seed phrases. A single seed phrase can derive countless Nostr IDs. Using a single Nostr ID across various Nostr apps focused on public notes is reasonable because users are sending public messages, and they can better accumulate reputation. However, for Nostr apps focused on private notes, users should use multiple IDs to achieve better privacy. For example, you could use ID1 for close friends and ID2 for work colleagues. Current chat applications provided by internet giants do not encourage users to use multiple IDs simultaneously because multiple IDs affect data mining, reducing the accuracy of user profiling and, consequently, advertising revenue. In this context, using only one ID is a bug, not a feature. If you use your Damus ID to chat with others on a Nostr app that focuses on private messaging, do you want all those people to see the public notes you have posted? A seed phrase that is universally applicable to all Nostr apps allows users to choose which ID to use in a particular app, with the ID generated from the seed phrase. This is far better than using a single Nostr ID across all Nostr apps. Don't forget, there are not only Nostr apps focused on public notes but also those focused on private notes. A reasonable chat app allows users to use multiple IDs simultaneously, whereas a microblogging app’s DM often has only one ID. This is just one of the differences between the two. When we say, "Designing a DM for a microblogging app is not the same as designing a chat app," we are not playing with words; we are not that bored.

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.

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.

One identity across all applications is a better user experience. I don't believe this is the way. nostr:nevent1qqs02uajmklxqk7xce5ha4ffs5rvgns5yhyt47zm30zw65qdq44t79qpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsyg9mly364yjxqe0c33qv0kdlv8xvcrlnlnlsvk5vktl5e7akyzy0rcpsgqqqqqqslqwukc

nostr:nevent1qqs02uajmklxqk7xce5ha4ffs5rvgns5yhyt47zm30zw65qdq44t79qpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtczyzaljga2jfrqvhugcsx8mxlkrnxvplelelcxt2xt9l6vlwmzpz83uqcyqqqqqqgppueea h/t nostr:nprofile1qqsth7fr42fyvpjl3rzqclvm7cwves8l8l8lqedgevhlfnamvgyg78spz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3qamnwvaz7tmwdaehgu3wwa5kuegpz4mhxue69uhk2er9dchxummnw3ezumrpdejqj9swg4

If you use your Damus ID to chat with others on a Nostr app that focuses on private messaging, do you want all those people to see the public notes you have posted? yes In fact, the first version of Keychat used nsec. Later, we intentionally switched to seed phrases. please bring this back