PABLOF7z on Nostr: no, people need to not overweight NIPs or the NIPS repo so much; you can implement ...
no, people need to not overweight NIPs or the NIPS repo so much; you can implement whatever you want on nostr without every touching the NIPs repo.
My process when I want to come up with a new use case is:
* search the repo and nostr for conversations about my use-case.
* look for a kind that isn't used (REQing random numbers I like)
* make up the schema I want.
* start using it.
* After a while I might create a NIP to document it so other people know it's there.
Both first and last step, which might touch the NIPs repo are optional. Particularly if a use-case takes off, the last step is largely irrelevant since the real-world implementation is the spec.
Published at
2023-11-14 10:51:22Event JSON
{
"id": "6c50846a1a8427916ca40f54d3e7a4da7cb74908a1e131098d46af9c2b88658a",
"pubkey": "fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52",
"created_at": 1699959082,
"kind": 1,
"tags": [
[
"e",
"04376973c41ca2fdbb7b68469679c102f796210fcb4fd1d1197a0ed919899a62",
"reply"
],
[
"p",
"de7ecd1e2976a6adb2ffa5f4db81a7d812c8bb6698aa00dcf1e76adb55efd645"
]
],
"content": "no, people need to not overweight NIPs or the NIPS repo so much; you can implement whatever you want on nostr without every touching the NIPs repo.\n\nMy process when I want to come up with a new use case is:\n* search the repo and nostr for conversations about my use-case.\n* look for a kind that isn't used (REQing random numbers I like)\n* make up the schema I want.\n* start using it.\n\n* After a while I might create a NIP to document it so other people know it's there.\n\nBoth first and last step, which might touch the NIPs repo are optional. Particularly if a use-case takes off, the last step is largely irrelevant since the real-world implementation is the spec.",
"sig": "523342e143347f781494775b074d0295530eb7f9aa2e7cf6c1c0543f9fbdc6ad246f14fdb75400378f7174511a9dd5f364e4146c895be8e0dadbf32da7d9c364"
}