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.

Reply to this note

Please Login to reply.

Discussion

For profile changes, best to blastr it

the protocol spec needs a distinction about broadcast vs outbox kinds

0, 1, blast... 4, outbox

Lots of sloppy caching happening client side.