hzrd149 on Nostr: 1. Read through the NIPs and if your use case sounds somewhat like what they are ...
1. Read through the NIPs and if your use case sounds somewhat like what they are designed for. look into using them, otherwise invent your own and ask for a lot of feedback from other devs
2. Pick your favorite number. your birthday. the birthday or your cat. anything as long as you are reasonably sure your not going to conflict with other developers. (you can check this by querying popular relays)
3. Draft a new NIP before your finished. IMO the purposes for NIPs is to *invite* other developers to work with you by explaining to them how your data is structured and what its used for
4. Write it as simple and strait forward as you can, don't explain why users use your app / event kind. instead try to explain to other devs how they can use your new event kind
5. IMO there really isn't a "process". the closest thing we have to a process it the requirement that at least two independent clients implement the standard. beyond that its just developers arguing on the internet...
I would say a good way to think about NIPs is "an invitation for integration". your not writing a standard that will be enforced on other developers. your writing an invitation to ask them to work with you. and generally invitations are best kept short and to the point (think of wedding invitation cards)
Then if they accept, you get to share users and both your apps get better
2. Pick your favorite number. your birthday. the birthday or your cat. anything as long as you are reasonably sure your not going to conflict with other developers. (you can check this by querying popular relays)
3. Draft a new NIP before your finished. IMO the purposes for NIPs is to *invite* other developers to work with you by explaining to them how your data is structured and what its used for
4. Write it as simple and strait forward as you can, don't explain why users use your app / event kind. instead try to explain to other devs how they can use your new event kind
5. IMO there really isn't a "process". the closest thing we have to a process it the requirement that at least two independent clients implement the standard. beyond that its just developers arguing on the internet...
I would say a good way to think about NIPs is "an invitation for integration". your not writing a standard that will be enforced on other developers. your writing an invitation to ask them to work with you. and generally invitations are best kept short and to the point (think of wedding invitation cards)
Then if they accept, you get to share users and both your apps get better