Replying to Avatar <old>cypherhoodlum

Decentralising NIPs might break the indexing completely. We might have seventeen NIP-41s and no way to do a key rotation reliably.

That being said even if the NIPs repository is centralised it has no way to enforce bad decisions in a tyrannical way. Client devs are "free farmers" and can do whatever they want but it is in their best interest to follow the interoperability train most of the time. The users keep client devs in check.

A centralised NIPs repository is not a bad thing.

nostr:nevent1qqs0wkak3n7fxta7f902u03rdpam8kxtljwxal4xczelujn3a888a0qpz3mhxue69uhhyetvv9ujumn0wd68ytnzvupzpms35h0lgrqe542lg8ly9dy0qrnp3jgjy43z4cmmds4mv7mkcnjfqvzqqqqqqyyc7t7v

Avatar
ulrichard 2y ago

You could host the NIP repository on radicle. Then there would be no central server. But there would still be a list of people with merge permissions, which one can also interpret as centralization.

Reply to this note

Please Login to reply.

Discussion

Avatar
<old>cypherhoodlum 2y ago

A long-term goal of mine (and the team) is to get the NIPs repo on GitNestr eventually. Centralised permissions, decentralised hosting.