All your metadata of your profile is published with a event of kind 0, see NIP-01: https://github.com/nostr-protocol/nips/blob/master/01.md#kinds
0: metadata: the content is set to a stringified JSON object {name: <username>, about: <string>, picture: <url, string>} describing the user who created the event. A relay may delete older events once it gets a new one for the same pubkey.
Normally every client should check if you have published a newer event with this kind and tries to look for it on a certain relay. This is where the pain begins...because every client has maybe integrated some caching and/or other logic to request & check that info...
In similar I can feel your pain with my own expierences which is related how different clients have implementated the different NIPs for a relay selection. For example, look at this recent note for some deeper-analysis with different client developers: https://snort.social/e/nevent1qqsfud7l89zftr28ljvye0xmygkk9un9xtl276s82eyn7gnr5nnasugzyqrx8x3cdjwpq9ppwc3ve085pyyvfudqcvlz87xk668540m9t78hzj9mz5a
Please remember, it's still very very very early with Nostr.
Using less relays is maybe something you could try. If you're debugging this, you should start using just 1 relay with different clients.
Went back to my Snort client, removed some of the relays, now even more DMs are missing. Nostr is unusable.
reply
Maybe now you've deleted the relay where your DM live...when using Snort I expect to use the Snort relay as one of your defaults. Use your frustration to master Nostr, I know you can ;-)
reply
But i had so many Relays, how come my DMs didn't got saved in them? It makes no sense.
reply
Al the sense, logic and other smart things are be found in the clients. @kieran is the builder of Snort, he knows the answer
Case is it’s all very complicated like many other topics within Nostr as wel. But I’m still a big fan… Nostr is a quite simple protocol, the problem is of all different implementations of the NIPs in the apps. And then you have suddenly unexpected behaviour in clients…
reply