Interesting..
Multiple profiles?
How does that work?
#asknostr
I'm very! thankful for the #zaps, but a little annoyed that sometimes they're still going to my WoS which I unlinked from my profile months ago.
I guess it makes sense there could be multiple versions of my profile out there.
But...sender of said zaps is not on any relays that I used to be on but have since left, so I don't think this is an "orphaned profile" situation.
I don't get it.
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z
#plebchain
Discussion
Some relays still have your old profile.
If you were using a given relay set in the past, changed your profile there (so all of them got updated) then removed a few relays from the list and updated your profile again, the relays you removed did not receive the update.
So, if apps are using those relays, they get your old version.
That's what I thought, ty. Maybe paid relays should allow free posting of profile updates?
Do you know which relay has your old info?
No, that's what is confusing me. Sender of zaps is not connected to any relays that I have left. At least I don't think, in early days some clients autoconnected so maybe I just need to connect to all of sender's relays long enough to update profiles...
...or connect to a timestamped profile sync/consensus relay?
I may not understand this correctly, but I think:
Say I join relay A and post an update to my profile - call it Profile v0.
Then I later disconnect from relay A, join relay B, and post a revised profile there - call it v1 - v1 would not replace the v0 on relay A because I'm no longer publishing there.
Someone follows me and is connected to relay A but not relay B. When they zap me it goes to my address per v0, not v1.
This may be a necessary evil of decentralization, but would be nice if we could fix it. I called it the "orphaned profile" problem.