Yeah. So DMs on nostr are notoriously hit or miss. You're going to get them but might be a delay. May be in your inbox but no notification or may have already read it but getting a new notification anyway.
Same with the other notifications. Jumping between multiple clients makes it worse. Some relays are recording that you acknowledged that one but not the other and they are not synched then the other client is loading one relay and not the other, etc.
The (at) is more on the client side. Some have a better faster integration than others.
Welcome to nostr. It's still new technology and pieced together by volunteers all with different ideas on how the code should work. It's amazing how much smoother everything is now compared to a year or two ago. It will continue to improve with time but some of those things are just because it is all decenterlized and not all coming from a single server or provider.
Using your key pair is not logging into your "account" cached somewhere on a single server. You are pinging a entire network of relays scattered all over the planet running from someones house or cloud account. Everything will eventually be received and synched with every relay but a time gap will exist. It used to be much worse but more relays and better relay code is smoothing that out.
GHOST
npub18d…lh8x3
2024-09-06 10:34:45
in reply to nevent1q…7gt8
Author Public Key
npub18dlusgmprudw46nracaldxe9hz4pdmrws8g6lsusy6qglcv5x48s0lh8x3Published at
2024-09-06 10:34:45Event JSON
{
"id": "0d6e761ebfcc99e69d7eff7c230e72ec20abc457e12190d2788740d7385bb42b",
"pubkey": "3b7fc823611f1aeaea63ee3bf69b25b8aa16ec6e81d1afc39026808fe194354f",
"created_at": 1725618885,
"kind": 1,
"tags": [
[
"e",
"9b8f1a7486e6de9f8ce24ca8bf9215be9ec0c9138f0cbd502331ee6e1750c751",
"",
"root"
],
[
"e",
"365bc214868c3643434ee60fc293f981b91cce228bef68e54c55a7bf83c1f568"
],
[
"e",
"762fb809803301b6fc6f239902c7edffd2fb9a1ca84ef43a62ce789cd799466f",
"",
"reply"
],
[
"p",
"3b7fc823611f1aeaea63ee3bf69b25b8aa16ec6e81d1afc39026808fe194354f"
],
[
"p",
"e0e92e542d79b28e79c6efe95891d38f49636e48560a8e618b953bded630dfaa"
]
],
"content": "Yeah. So DMs on nostr are notoriously hit or miss. You're going to get them but might be a delay. May be in your inbox but no notification or may have already read it but getting a new notification anyway. \n\nSame with the other notifications. Jumping between multiple clients makes it worse. Some relays are recording that you acknowledged that one but not the other and they are not synched then the other client is loading one relay and not the other, etc. \n\nThe (at) is more on the client side. Some have a better faster integration than others. \n\nWelcome to nostr. It's still new technology and pieced together by volunteers all with different ideas on how the code should work. It's amazing how much smoother everything is now compared to a year or two ago. It will continue to improve with time but some of those things are just because it is all decenterlized and not all coming from a single server or provider. \n\nUsing your key pair is not logging into your \"account\" cached somewhere on a single server. You are pinging a entire network of relays scattered all over the planet running from someones house or cloud account. Everything will eventually be received and synched with every relay but a time gap will exist. It used to be much worse but more relays and better relay code is smoothing that out. \n\n",
"sig": "c05a38ecd4ba9f9ade1d60f9424db53529dc265e1d67a79b5c8f0a65c1e4e2212a9a318500cf881f78a9d8921378439618e5b43054e4b29b64c4cb9266bf532b"
}