notonbirdapp on Nostr: I was playing around with nostr. Had my original nsec/npub pair generated in ...
I was playing around with nostr. Had my original nsec/npub pair generated in amethyst, recently connected it with
Alby (nprofile…qss4) and started using alby extension to log in to different clients on desktop.
I've noticed @iris was showing different npub than amethyst - so went to alby and found you can put in different npub in settings - which gave me a bit of head scratching... How does it work? - Can I put any npub there? But eventually putting my npub from amethyst into Alby settings (nostr nip-05) didn't change anything, logged out and in a few times and it still shows different npub.
Same with
Satlantis (nprofile…pzsw) - logging in using @Alby shows same npub as iris which is different to the one I'm using in amethyst...
Does it mean that if I'm using Alby as login option it generates new npub once (derived from original) and uses it for any other service? Is it some sort of bug? Or I'm just being stupid and been using two different nsec... I think I might have previously generated different nsec/npub pair with iris on this machine, so I found switch user button and logged in using alby extension. Seemed to work fine.
But it turns out that it (@iris) still treats me as different npub than @Amethyst.
Can someone help me understand what I'm doing wrong? #asknostr
Published at
2024-10-11 21:20:41Event JSON
{
"id": "de6019c163c103f3bbffa6b13b01e2b0ab8122c36e4b6f89423bb40934693599",
"pubkey": "648199ac87906f22be25222ffba07a330275dd6cdb881d8d234465978b4d941d",
"created_at": 1728681641,
"kind": 1,
"tags": [
[
"p",
"4657dfe8965be8980a93072bcfb5e59a65124406db0f819215ee78ba47934b3e",
"",
"mention"
],
[
"p",
"a19aadee53bc71d25afef365067a3978ac30d5520d36ec8cc74d77a872af7359",
"",
"mention"
],
[
"t",
"asknostr"
]
],
"content": "I was playing around with nostr. Had my original nsec/npub pair generated in amethyst, recently connected it with nostr:nprofile1qqsyv47lazt9h6ycp2fsw270khje5egjgsrdkrupjg27u796g7f5k0spzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgwwaehxw309ahx7uewd3hkctcprdmhxue69uhkummnw3ez6vfwde3x7tnpdenkzmnf9e3k75xqss4 and started using alby extension to log in to different clients on desktop. \n\n\nI've noticed @iris was showing different npub than amethyst - so went to alby and found you can put in different npub in settings - which gave me a bit of head scratching... How does it work? - Can I put any npub there? But eventually putting my npub from amethyst into Alby settings (nostr nip-05) didn't change anything, logged out and in a few times and it still shows different npub.\nSame with nostr:nprofile1qqs2rx4daefmcuwjttl0xegx0guh3tps64fq6dhv3nr56aagw2hhxkgprdmhxue69uhkummnw3ez6ur4vgh8xetdd9ek7mpwv3jhvqgjwaehxw309ac82unsd3jhqct89ejhxqgkwaehxw309ahx7um5wgh8xarpddjhjtnwv46qgapzsw - logging in using @Alby shows same npub as iris which is different to the one I'm using in amethyst...\n\nDoes it mean that if I'm using Alby as login option it generates new npub once (derived from original) and uses it for any other service? Is it some sort of bug? Or I'm just being stupid and been using two different nsec... I think I might have previously generated different nsec/npub pair with iris on this machine, so I found switch user button and logged in using alby extension. Seemed to work fine. \nBut it turns out that it (@iris) still treats me as different npub than @Amethyst.\nCan someone help me understand what I'm doing wrong? #asknostr \n",
"sig": "c48aaeacbe33ae82d5bcb0d136502c8e59a64c7781b289468f8b9d8669c495e3887dd389173a6e3fdc9a5e2e66a887a2db32f8fc18a749cb8b7a321343bb68da"
}