n1.g1.n1

"0432b01fb08328b320c2190e251d145274f6f857b3ff91da5269140da553f317a4e89de21ec31d7c5d1dee85d546c72aed46d9aff40f99c2f37ae3fc50aa8bcd"

Last Notes

2026-03-26 19:00:12 UTC

- reply

Thanks for answering, @nprofile…x9xy . I don't think I can talk about most teams' experiences now, since **my use case** is to actually open the door to bring in collectives that are still not here (they live inside a project I work with called Socialroots). One major need we have (and this is based on a decade of user-research) is for the collective concept to be more flexible than the usual list of members in a server. Long (design) story short: **Collectives need to be able to connect in networks**, which means sharing permissions to common resources and sub-groups. I came up with three broad/reusable concepts to implement in the Nostr space: Collectives + Capabilities + Commons (which you can read more about in the same repo).
All that to get to the Policy-based Signer: If collectives are represented by nostr-native identities (npub), we'd get a lot of the social-graph flexibility by default, BUT we need a shared **governance model for those identities**. Stewards need to agree on the policies that the signers must enforce. The main proposal for the policy-based signer is to convert the policy into Nostr kinds. That would help with policy design outside the signer, improve transparency in multi-steward approval procedures, and allow for policy reuse across signers. (Side note, I would like some of those properties even as an individual user.)
I hope this helps.

2026-03-25 23:15:09 UTC

Hey, @nprofile…saf9 @nprofile…dz5r @nprofile…5pnl. As part of my Collectives project, I was thinking about collective-key management and, with much delay, got to look into the **KeyCast project**. Do you think **standardizing the policy-based signing** is a good move? At least from the perspective of a collective, having policy transparency and requiring stewards to sign the policy before it can be enforced feels like it makes sense. If you have any spare cycles, I've put together some ideas here: https://github.com/nigini/nostr-collectives/blob/main/DOCS/Policy-Based-Signer.md (feel free to open issues or respond here.)

2026-03-11 17:30:18 UTC

- reply

Sounds like a great idea! I am also a member of the social.coop and I am pretty sure people there would be happy to share their experiences. Count me in at least for "business" analysis! ;)