Edit profile deletes metadata set in other nostr client

[josefinalliende]

Context

I have a White Noise account connected to Primal relays.

• I added a profile picture in Primal → the metadata in Whitenoise did not update.
• Then, I edited my profile in Whitenoise (just changed the name) and saved.
• After that, in Primal my profile picture was lost.

It seems like saving profile edits in Whitenoise overwrites existing metadata fields (such as the profile image), even if they weren’t changed.

Solution

• Investigate why metadata is being overwritten.
• If a user already has a profile image (or any metadata field) and it wasn’t changed during the edit, it should not be replaced or removed.
• This behavior should apply consistently to all metadata fields, not only the profile image.

[untreu2]

In Nostr protocol, all of the user's metadata is in a single event. If you update a metadata that has a profile picture with one that doesn't, you'll lose your profile picture. This means that fields can't be updated individually.

[josefinalliende]

Yes, I know. But from the user’s perspective, they only changed their name, so nothing else should be lost.

That’s why we need to be careful with all metadata fields, especially the ones we don’t explicitly use. I mean that when we build the metadata, we need to preserve all existing fields from the latest kind 0 event except the ones we edited.

And that was broken. But now I'm testing in you branch and it is working fine... So I guess the real issue was that the metadata wasn't updated before editing. Once your PR is merged, I think we can close this one!

[untreu2]

So #560 fixed this?

[josefinalliende]

Nope, sadly it is still happening 😨

[josefinalliende]

Ok, but I found the fix and it was really easy haha... jus invalidating the active account provider in the polling provider works, now active account metadata seems to be updated 🎉 I'have a draft PR with metadata changes, will include that fix there.