mattybs on Nostr: I updated the lightning address on my profile yesterday. I did so via noStrudel and ...
I updated the lightning address on my profile yesterday. I did so via noStrudel and Snort, and made sure that any clients I tried showed the updated profile.
Everything appeared to update except for jnump.me, and I never figured out what relays that is looking at to understand any profile changes.
But strangely enough, checking my nostdress logs, it seems like there are more references out there to my old lightning address than new one, because I'm still seeing tons of lookup failures referencing the defunct address.
Again, I made this change yesterday, so it will be interesting to see when these errors finally dry up -- which I would interpret as propagation.
Published at
2024-04-28 17:56:46Event JSON
{
"id": "368d436ffc0f4f635a1a2858102c0226f0996aa7c87eed2b0d7f9cd55280e273",
"pubkey": "faaf47af27e3de06e83f346fc6ccea0aabfc7520d82ffe90c48dfcd740c69caa",
"created_at": 1714319806,
"kind": 1,
"tags": [],
"content": "I updated the lightning address on my profile yesterday. I did so via noStrudel and Snort, and made sure that any clients I tried showed the updated profile.\n\nEverything appeared to update except for jnump.me, and I never figured out what relays that is looking at to understand any profile changes.\n\nBut strangely enough, checking my nostdress logs, it seems like there are more references out there to my old lightning address than new one, because I'm still seeing tons of lookup failures referencing the defunct address.\n\nAgain, I made this change yesterday, so it will be interesting to see when these errors finally dry up -- which I would interpret as propagation.\n\n https://i.nostr.build/ml9Eq.png",
"sig": "2e9272ea495cf5caa6c40ae445a82fc9ce247a6103426396311f44359e05453f991dd6c450bdc78b73454d384f01b2bb6ba3538feb39111dd75592a4e02808cb"
}