2025-09-02T23:06:25Z https://yabu.me n1.g1.n1 https://yabu.me/npub1vjhrl4k2uj6sttu5y3xahz29esk2nfn274de8qtn5jkv06zwn7gs68ejkd https://npub1vjhrl4k2uj6sttu5y3xahz29esk2nfn274de8qtn5jkv06zwn7gs68ejkd.blossom.band/a858b4d4d32c97eced7740d4a2ce93f61a3ac7e380895105d7ab34e606a84382.png https://npub1vjhrl4k2uj6sttu5y3xahz29esk2nfn274de8qtn5jkv06zwn7gs68ejkd.blossom.band/a858b4d4d32c97eced7740d4a2ce93f61a3ac7e380895105d7ab34e606a84382.png https://yabu.me/nevent1qqs0v65dfsg3c9nwksp94l00hd5neffsvx997zujn9m84srmpfpvjpqzypj2u07ketjt2pd0jsjymkufghxze2dxdt64hyupwwj2e3lgf60ezeut0n6 In reply to <a href='/nevent1qqsp5ua7qvyvqdne4x86thh74fvm93avp2lr5hchzxlecn20azu8decppemhxue69uhkummn9ekx7mp0qn5n8a'>nevent1q…5n8a</a><br/>_________________________<br/><br/>Thanks for answering, <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/nprofile1qyt8wumn8ghj7un9d3shjtn2v4nxveewveukjtcppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qpqzuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsudx9xy" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>JeffG</span> (<span class="italic">nprofile…x9xy</span>)</a></span> . I don&#39;t think I can talk about most teams&#39; 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). <br/><br/>All that to get to the Policy-based Signer: If collectives are represented by nostr-native identities (npub), we&#39;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.)<br/><br/>I hope this helps. 2026-03-26T19:00:12Z https://yabu.me/nevent1qqsy2ql2zdct6usarn9np45j6hpvytal8qjgf7zx8vt9l4w0dg6nd8czypj2u07ketjt2pd0jsjymkufghxze2dxdt64hyupwwj2e3lgf60ezgdra37 Hey, <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgkwaehxw309aex2mrp0yhx5etxvenjuenedyhszxthwden5te0wpex2mtfw4kjuurjd9kkzmpwdejhgtcqyqtnnkfhmjxqcums4gn4skfccyv7yhzp7mzyrfwnf3kns5p7xymw7a8saf9" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>JeffG</span> (<span class="italic">nprofile…saf9</span>)</a></span> <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgawaehxw309a3k7mtdw4hxjarfv4ejumn0wvh8xmmrd9skctcppemhxue69uhkummn9ekx7mp0qqsgnmujh847dhq7f63e3aj80u38a92zjcnmpgeaezdkgrsn0vjkhegz4dz5r" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>dcadenas</span> (<span class="italic">nprofile…dz5r</span>)</a></span> <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/nprofile1qyghwumn8ghj7mn0wd68ytnvv9hxgtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qpqwmr34t36fy03m8hvgl96zl3znndyzyaqhwmwdtshwmtkg03fetaqzn5pnl" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>rabble</span> (<span class="italic">nprofile…5pnl</span>)</a></span>. 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&#39;ve put together some ideas here: <a href="https://github.com/nigini/nostr-collectives/blob/main/DOCS/Policy-Based-Signer.md">https://github.com/nigini/nostr-collectives/blob/main/DOCS/Policy-Based-Signer.md</a> (feel free to open issues or respond here.) 2026-03-25T23:15:09Z https://yabu.me/nevent1qqsr8fke4zgu4wcmfs2mc2ztdcgejn9rleeuuyepqm0kr2zyktw8ujqzypj2u07ketjt2pd0jsjymkufghxze2dxdt64hyupwwj2e3lgf60ezsquflg In reply to <a href='/nevent1qqsqn4a0wf2hnuaa2g5hfl8elmcgkpuwvsthdly5h5vse05cp6mksygppemhxue69uhkummn9ekx7mp0pr2ufl'>nevent1q…2ufl</a><br/>_________________________<br/><br/>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 &#34;business&#34; analysis! ;) 2026-03-11T17:30:18Z