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:

nostr:nevent1qvzqqqqqqypzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqytkummnw3ez66tyvgaz7tmrv93ksefdwfjkccteqqstqqprcjtg6pwut78squstta40qqqfr062y96zjgd2z52kg4k4s3c892uhx

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).