yes, any event in the k >= 30000 < 40000 is a replaceable event and should have a "d" tag as an identifier (preferably random)

https://github.com/nostr-protocol/nips/blob/master/01.md#kinds

Reply to this note

Please Login to reply.

Discussion

I see

So in this case where nostr:nprofile1qyt8wumn8ghj7ct5d3shxtnwdaehgu3wd3skueqpz4mhxue69uhk2er9dchxummnw3ezumrpdejqqgqw2gfz684etnwchf0ktq2l05wfzfdgc9xc9xy74ef2kd57afk8usm9px6j is asking to edit an existing collection:

The UI would call the latest collection, allow the user to add gifs and then publish a new event with a new/random 'd' tag that can be retrieved by it's latest "created at" time

Makes sense, thanks!

What's the point of the 'd' tag actually if it's just pulling the latest event?

Events in the k>=10000<20000 are replaceable by kind. So each pubkey only has one of them. A good example is the k:10002 events

Events in the k>=30000<40000 are replacable by "d" tag. So when a new event is published it replaces the old one with the same "d" tag. A good example would be the NIP-23 article events