NIP type field

[kehiy]

Beside optional and draft tags which determine the status and priority of a NIP, I think we need to add another field that determines whether this NIP must be implemented by relays/clients or both.

[bezysoftware]

I agree. Frankly I think we should also somehow categorize the NIPs / have a separate UI which will categorize NIPs based on this new tag.

I want to track changes in the NIPs relevant to me (relay-based ones), but now my only option is to opt in for notifications on ALL changes in this repo and then mute those which are not relay related.

[kehiy]

@bezysoftware yes. adding tags on the top of nips + having github labels, will help developers to manage it better.

[kehiy]

for nips we can do that. but for github tags, members must do that, we can't.