Thread

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??
lostcause's avatar lostcause
NCC-00: Publishing Nostr Community Conventions on Nostr
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.
Read article →

Replies (1)

So - following on from the previous post - which proposes a system call Nostr Communities Conventions (NCC for short) - I vibecoded a #python app that works as a proof-of-concept for creating, publishing NCCs - and the other aspects like succession records and NCC endorsements. It's not pretty, but seems to work - bonus! You can have a play from the #github repo at
GitHub
GitHub - imattau/nostr-community-conventions: Nostr Community Conventions exist to document **shared usage patterns** of existing Nostr primitives where protocol-level standardisation is unnecessary or undesirable.
Nostr Community Conventions exist to document **shared usage patterns** of existing Nostr primitives where protocol-level standardisation is unnece...
lostcause's avatar lostcause
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?? View Article →
View quoted note →