הצטרף ל-Nostr
2026-06-05 14:08:54 UTC
in reply to

jaredlogan on Nostr: Custom d-tags for app (kind 31990) events. nostrhub generates a random d-tag, which ...

Custom d-tags for app (kind 31990) events. nostrhub generates a random d-tag, which is spec-compliant, but it locks the app event's addressable identity to whatever you pick server-side. Two consequences:

1. The 31990 event is replaceable by (pubkey, kind, d). I can't update the same event from another client without manually matching that random d-tag, so editing elsewhere risks forking into a duplicate app event.

2. When the app publishes its own notes, the `client` tag coordinate (31990:<pubkey>:<d>) has to embed the d-tag to render the linked "via [app]" attribution. A chosen, stable slug is far easier to wire into the app's publishing code than a random string.

Could you let authors set the d-tag on publish, or at minimum surface the
generated one as editable if possible? I've been having to go to nostrudel to build the custom app event initially to get this to work as I want it to.