TKay @TKay - 18h
You know what I realized I want on nostr! NIP Proposal: nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z It would be great if I can sign an event similar to followers, (but they are all my random keys). My other npubs. I want to be able to generate a random key pair for the Other Stuff or clients. For example Olas. And announce to others that the secondary account is also mine. And the. automagically clients will mask the random key with my main profile. #nostr #nip
Or is this practically impossible?
TKay @TKay - 17h
I think I’m not explaining it well enough. I want to have two key pairs (or more), but I want my main one to announce it’s “adopting” the other. then second can handshake this relationship with my main account. Once that is done. I can use my second key pair npub with close to zero risk. If it gets compromised in an insecure app, the main key will denounce it. If someone wants to send me a dm to the secondary npub, the client will look for the main one and send it. I feel like I’m not making sense 🤣😅 this needs a nostr nest.
What I don’t understand, Vitor says that DMs, notifications, mentions etc won’t reach the main account, why? Let the client tag, DM, Mention, both npubs, sub and main. No?
I don’t know, this makes sense to me. lol I convinced my self 🤣 Brainstorming in notes is impossible.
Yeah, almost like this. But this is waaay more complicated and “official”. I’m thinking of something much simpler. Exactly the same way I publish my follow list, I thinking of a Kind to publish my alt accounts. (Clients can do what they want with this info). And people will know if they see a random post from another app that that’s also me, just under a different pubkey. Makes sense?
