melvincarvalho on Nostr: If we were to add the latest timestamp to nostr-did, and ensure it is not overwritten ...
If we were to add the latest timestamp to nostr-did, and ensure it is not overwritten by an older timestamp, it would be possible to solve the consistent profile, and buggy following UX in nostr. NIP-05 providers could simply point to a DID and update it on the server, or allow the user to update it via NIP-98. Some providers would offer it as a paid service, others offer it for free.
https://nostrcg.github.io/did-nostr/Published at
2025-03-30 13:43:58 GMTEvent JSON
{
"id": "e34b0ba107289c4cad457bb923576682002249fa5c033ef90335ffcdf70d6697",
"pubkey": "de7ecd1e2976a6adb2ffa5f4db81a7d812c8bb6698aa00dcf1e76adb55efd645",
"created_at": 1743342238,
"kind": 1,
"tags": [
[
"r",
"https://nostrcg.github.io/did-nostr/"
]
],
"content": "If we were to add the latest timestamp to nostr-did, and ensure it is not overwritten by an older timestamp, it would be possible to solve the consistent profile, and buggy following UX in nostr. NIP-05 providers could simply point to a DID and update it on the server, or allow the user to update it via NIP-98. Some providers would offer it as a paid service, others offer it for free.\n\nhttps://nostrcg.github.io/did-nostr/",
"sig": "dcdab54ecc523593843cb721e5e6a01dceb1426028dcf39565b5910c12acbf2b2448ed329beb300874fbb264a214ef1f3e8d20efe181bc0ee6f9edd7493dc52a"
}
