And here is a PR for CLI geeks: https://github.com/fiatjaf/nak/pull/62
Pinstr is using a special event kind "33889" for the boards of pins of any type. And honestly no one is using Pinstr anymore! No one cares! So keep rocking with following.space! π
actually following.space is the next Pinstr.app π

it's just a placeholder and not working yet π but I'll implement it later!
nostr:npub1l77twp5l02jadkcjn6eeulv2j7y5vmf9tf3hhtq7h7rp0vzhgpzqz0swft nostr:npub18c556t7n8xa3df2q82rwxejfglw5przds7sqvefylzjh8tjne28qld0we7 nostr:npub1qe3e5wrvnsgpggtkytxteaqfprz0rgxr8c3l34kk3a9t7e2l3acslezefe what do you think? https://github.com/nostr-protocol/nips/pull/1847
Primal kinda hid this note from meβdidnβt even get a notification. I only saw it thanks to my very own Nostribe! π Not saying Nostribeβs better or anything, lol. Anyway, sorry for the late reply! Iβll catch up on the discussion on Github.
I think the builder decides what's advanced and what's not π§
It's in a stable version. You can still use it. But nostr:nprofile1qqs8suecw4luyht9ekff89x4uacneapk8r5dyk0gmn6uwwurf6u9ruspzpmhxue69uhkummnw3ezumt0d5hsz8thwden5te0dehhxarj9e3xjarrda5kuetj9eek7cmfv9kz7s4pntl doesn't like it anymore!
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).
thanks for your support of Pinja π«π«π«
URLs are inside the content of the Nostr Events. Searching events by content is not working well in Nostr.
NOSTR TAUGHT ME TO SKIP THE COMPLAINTS AND FOCUS ON BUILDING, NO EXCUSES.
π New Pinja Enhancements:
β You can now include a βDescriptionβ with each pin.
β You can also add βHashtagsβ to your pins.

π₯²
Thank you, sir. I don't know... I'm seeking a way to create more value for the community.
Here is a list of Nostr Apps that I've been working on directly in the past 2 years:
Nostribe: X on Nostr
Pinja: Pinboard on Nostr
Docstr: Google Docs on Nostr
Pinstr: Pinterest on Nostr
Groups: Telegram on Nostr
OPAL: Ending homelessness with Nostr & Bitcoin
NostrPlayground: Query relays with beauty

