If we had infrastructure for curating entries, allowing grou...

3bf0c63fcb934634...

npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6

hex

4cb864f6eedbd74c2c6bb6a93e13fac48b9cc0db985ecf81e8c95a925c5dc066

nevent

nevent1qqsyewry7mhdh46v934md2f7z0avfzuucrdeshk0s85vjk5jt3wuqesprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gyyskcn

Kind-1 (TextNote)

2026-03-23T16:27:55Z

If we had infrastructure for curating entries, allowing groups to vote on proposed additions and deletions and simple UIs for viewing the list of all items in a list then it would be easy to get rid of the NIPs repository.

It's sad that after so many years all we have are "feed" views. And GitHub continues to be a better platform for browsing and updating text lists of things. Notice that I'm not asking for much.

We would also have to get rid of the NIP numbers, but we could just say "the longform NIP", "the badges NIP" etc and it wouldn't be hard to know what were people talking about.

But if you're reading this and thinking about a complicated system with events being published with votes, proposals, lists of replaceable events with other lists inside or whatever absurdity, please stop. Just use a relay and normal events inside, add and delete. Custom write policies, standard Nostr read API.

#pyramid has a moderated subrelay that is probably 25% there already.

If you disagree please let me know.

nostr:nevent1qvzqqqqqqypzpem34u9stj8ftlxldl4n2qz5f5hmrnxns3uga86fpwe7u28ga4n0qyvhwumn8ghj7mrfva58gmnfdenjuun9vshkjmnzdauqqg94qxruwu659epnqnpr5sunsg9fer6vdw5pxfhw6hzqw6hmvzzpdvjq8z8j

原始 JSON

{
  "kind": 1,
  "id": "4cb864f6eedbd74c2c6bb6a93e13fac48b9cc0db985ecf81e8c95a925c5dc066",
  "pubkey": "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
  "created_at": 1774283275,
  "tags": [
    [
      "t",
      "pyramid"
    ],
    [
      "q",
      "b50187c773542e43304c23a4393820a9c8f4c6ba81326eed5c4076afb608416b",
      "wss://lightning.red/inbox"
    ],
    [
      "p",
      "e771af0b05c8e95fcdf6feb3500544d2fb1ccd384788e9f490bb3ee28e8ed66f"
    ]
  ],
  "content": "If we had infrastructure for curating entries, allowing groups to vote on proposed additions and deletions and simple UIs for viewing the list of all items in a list then it would be easy to get rid of the NIPs repository.\n\nIt's sad that after so many years all we have are \"feed\" views. And GitHub continues to be a better platform for browsing and updating text lists of things. Notice that I'm not asking for much.\n\nWe would also have to get rid of the NIP numbers, but we could just say \"the longform NIP\", \"the badges NIP\" etc and it wouldn't be hard to know what were people talking about.\n\nBut if you're reading this and thinking about a complicated system with events being published with votes, proposals, lists of replaceable events with other lists inside or whatever absurdity, please stop. Just use a relay and normal events inside, add and delete. Custom write policies, standard Nostr read API.\n\n#pyramid has a moderated subrelay that is probably 25% there already.\n\nIf you disagree please let me know.\n\nnostr:nevent1qvzqqqqqqypzpem34u9stj8ftlxldl4n2qz5f5hmrnxns3uga86fpwe7u28ga4n0qyvhwumn8ghj7mrfva58gmnfdenjuun9vshkjmnzdauqqg94qxruwu659epnqnpr5sunsg9fer6vdw5pxfhw6hzqw6hmvzzpdvjq8z8j",
  "sig": "11f4c5b5a20cace3807391b57be614f80ad53f4b67b5da299c26759aa65889e229ff871c52077f7e3c9f67dd63505ebc36e052056daa88ac7b3e540fe06972df"
}