#Nostr101
"npub" is your public key. It never changes.
"nprofile" has both your public key and your current home relay. It changes as your outbox relay list changes.
When you are sharing your user, prefer to share it as an nprofile since the receiving user / app can quickly figure out where to get more information from the user.
If the receiving app only has the npub, it has to search for a relay that has the user. If the receiver is using the same relays as the sender, that's easy. But if the receiver is on a separate relay set, then it's likely the receiver will never load the user.
Outbox model fixes this but it requires you to share the nprofile, not just the npub.
Vitor Pamplona
npub1gc…fnj5z
2024-10-10 17:47:38
Author Public Key
npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5zPublished at
2024-10-10 17:47:38Event JSON
{
"id": "cadd19bf6f713811dd82d4f74bd0f7f1e58e5fb02a383e6c9409d0dd0094137b",
"pubkey": "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c",
"created_at": 1728582458,
"kind": 1,
"tags": [
[
"t",
"Nostr101"
],
[
"t",
"nostr101"
]
],
"content": "#Nostr101 \n\n\"npub\" is your public key. It never changes. \n\n\"nprofile\" has both your public key and your current home relay. It changes as your outbox relay list changes. \n\nWhen you are sharing your user, prefer to share it as an nprofile since the receiving user / app can quickly figure out where to get more information from the user.\n\nIf the receiving app only has the npub, it has to search for a relay that has the user. If the receiver is using the same relays as the sender, that's easy. But if the receiver is on a separate relay set, then it's likely the receiver will never load the user.\n\nOutbox model fixes this but it requires you to share the nprofile, not just the npub.",
"sig": "2c4a2ed2638d96c150d0ad50e3dc524bf55a9c6507497016ba2610bacce308c9b67c8628797276d1ab026c7348a402480e84d94d2ed631b1468b2fae7f86750a"
}