Can somebody smarter than me figure out a way to “pin” notes? Do we need a new NIP for this?? #asknostr

Reply to this note

Please Login to reply.

Discussion

Bookmark?

I was under the impression that bookmarks were different than pins?

Oh probably. Not sure what a pin would be exactly? Like I could pin a note to the top of my profile for others to see type of thing?

Yep like if I’m hosting a zap stream and want to keep that announcement at the top for easy finding without having to repost it every day

I understand. I have a pin atm for the halving stream.

For a stream this would only work if you get a vanity url for zapstream like zap.stream/thegrinder. Each stream is a unique nostr naddr1 event. So the link changes with every new stream unless you have a channel url. You can get the url through snort.social.

You can feature a specific note, product, stream or whatever you deem important. On noStrudel a pin looks like this when you view someone's profile.

We already have it. Nip 51. Kind 10001 is a pinned notes list. It’s just up to clients to actually support it.

So not 32. Thanks!

No. 32 is labels.

Yeah. thanks for the correct nip!

So the NIP for pinning is the List NIP… interesting… I can see it

Ok so let’s say I created a “pinned notes list” in a client that supports it - are you saying my pinned notes would only appear to others at the top of my profile if someone visited my profile from a client that supports nip51? Ideally this kind of feature would be client agnostic I would think. 🤔

Yes, that’s right.

No feature can be client agnostic. Almost all of the nostr spec is “optional”. That’s a feature not a bug IMO.

pins should be an option in your client of choice. Snort has it, noStrudel has it, not sure about some of the other client. Also not sure if pins are a NIP. If they are then I'd assume it to be NIP-32, a label but that's a guess.

What I want is for anyone who visits my profile from any client to see certain pinned notes at the top… hmm. I’ll look at NoStrudels implementation.

Yeah so that would be NIP-51 as pointed out by nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc. If your client doesn't support that NIP then it's not "living the nip standard".

There is a nip for that, nip51. I'm not sure but I think you can see/manage that in Listr.lol