Can you guys please stop doing random "d" tags and instead use the URL as the "d" tag and put the comment on the content?
Last month nostr:npub1l77twp5l02jadkcjn6eeulv2j7y5vmf9tf3hhtq7h7rp0vzhgpzqz0swft and nostr:npub1zqcaun7cgynyaw6dapylz9cq7g4e62kj7z78hrklkwah2dcajyeqc9uza5 have started to work on a social bookmark client nostr:npub1mswm0kyce37jsnrwa3jelm469rcnezyq505djwl4aparmf4xf2es8rxl8w using Nostr (inspired by Del.icio.us from the past). Earlier this month they changed to event kind 39700 for broadcasting the Nostr events with the bookmark / link data accross the network. They did this because nostr:npub18c556t7n8xa3df2q82rwxejfglw5przds7sqvefylzjh8tjne28qld0we7 already created a social bookmark like client https://pinja.in when nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 raised this idea:
This morning I integrated this behaviour too on https://ccns.nostrver.se. So new created links are now broadcasted as kind 39700 events to several relays.
So we have now 3 clients using this kind number and I have some suggestions to improve the currently used event structure which I wrote down in this article:
nostr:nevent1qqstvgj6vp7c2zvh5dux84aca6pmhuq6nnlcpc99vekut4h4r5tvy7cpz3mhxue69uhhyetvv9ujuerpd46hxtnfdupzqpnrnguxe8qszsshvgkvhn6qjzxy7xsvx03rlrtddr62haj4lrm3fzdmxw (fallback URL: https://nostrver.se/blog/links-posted-ccns-are-now-broadcasted-nostr-events-kind-39700 for client who don't render those bech32 formatted keys).
Discussion
What is in my article:
As there is no NIP (yet) for this event kind, I see some possible improvements:
Use the bookmark URL value in the d tag so it can be used as a unique identifier for every client
Use the content field for the description value
Use the a tag for an addressable event following NIP-01: ["a", "39700:pubkey_of_author:", recommended_relay_url_optional]
Related: general comment on any URI (whether it’s a URL or something else like a book or a blockchain tx)
I definitely agree with the first 2, the 3rd I don't understand, the "a" tag could be added on subsequent (NIP-22) comments to the URL bookmark, and then it will include the "d" value, i.e. the URL.
That a tag always is confusing me..
For example when I follow NIP-23, kind 30023 events can have an a-tag too correct? If so, why not for other addressable events?
They don't have an a-tag generally, no. Only other events that refer to them.
pinstr.app was one of my favorites nostr:npub18c556t7n8xa3df2q82rwxejfglw5przds7sqvefylzjh8tjne28qld0we7 ...
wish you hadnt abandoned it.
It's in a stable version. You can still use it. But nostr:nprofile1qqs8suecw4luyht9ekff89x4uacneapk8r5dyk0gmn6uwwurf6u9ruspzpmhxue69uhkummnw3ezumt0d5hsz8thwden5te0dehhxarj9e3xjarrda5kuetj9eek7cmfv9kz7s4pntl doesn't like it anymore!