I’ve published a proposal for Nostr Community Conventions (NCCs).

The idea is simple:

NCCs are lightweight, Nostr-native conventions for client and ecosystem behaviour. Not protocol rules, not enforced standards. Just documented patterns that emerge, get copied, and evolve.

Key points:

- NCCs live on Nostr, not GitHub

- Numbered like NIPs, but optional and non-authoritative

- Authority comes from timestamps, signatures, and adoption

- Anyone can propose improvements

- Stewardship can be acknowledged, but community adoption still wins

The first paper, NCC-00, defines how NCCs themselves are published, revised, and evolved using Nostr events.

This is about making emerging norms legible, not creating a new gatekeeper. Feedback, forks, and competing approaches are expected.

Will probably try to make a proof of concept client at some point.... Python maybe?? nostr:naddr1qqgxxve58pnr2ef3xa3kzde58qerwq3qkhf5amw8mrupe649a5mhkk3d2d8wjj06urz6kwawpftk4f68tjlsxpqqqp65w6esaum