No. They aren’t. It would be super hard to do I think without significant changes to the NIP.
Are collaborative lists that permissioned users can add to a thing? nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc
Discussion
Damn, I didn't think so. Changes to which NIP? nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn mentioned NIP 32. This would be a great feature on listr.lol
Does NIP-51 with “a” tag support not do what you’re asking?
Bob and Charlie maintain lists of widgets. Alice makes a widgets list but instead of managing the list herself, she imports the items from Bob’s and Charlie’s lists.
I think this would create 3 separate lists, no? What I really want is one list with the ability to whitelist specific authors.
Doesn’t that accomplish exactly what you want? Alice has one list for which she has whitelisted specific authors. The existence of the other lists may feel a bit inelegant / uneconomical, but do they detract from the solution?
I suppose I’m imagining you have a dev to build a UI to make it feel like one list even though it’s multiple lists under the hood. But of course that won’t always be the case. Do you have specific application in mind?
I’m very keen on seeing curated lists become a thing in nostr, as I explain in my habla essay (summary of a talk I gave at Nostrville), so I’m curious to know what it will take to move us in that direction.
Yes, my specific use case would be to share bookmarks with members of the Nostr report team for curation of content, research, etc. Currently we do this using a combination of telegram and spreadsheets, but would love to move to a more Nostr centric workflow.
Would a general-purpose private group solve your use case?
Less so because we essentially store noteid's in a spreadsheet. I think what would need to move us away from something like Google sheets would be a curated list where we can whitelist contributors.
nostr:npub1arkn0xxxll4llgy9qxkrncn3vc4l69s0dz8ef3zadykcwe7ax3dqrrh43w had a cool idea for Yondar where an event owner can specify other npubs as admins and then clients can allow changes made by those npubs to show on the root event.
You could do something like that with any event kind.
Would that work with lists?