I was reading NIP-11 and I reached out maybe we can change and add some stuff there. Here are the details.
wildcard: For fields like relay_countries, language_tags, and tags we can support "*" as a valid value which indicates that all possible values are supported/applied. Or maybe the absence of these fields means the same thing? Or at least we have to make it clear what should they do to say we don't have it at all, we have specific ones, or we support/have all of them. or what behaviors can mean these?
Pay-to-relay: We need to add details in this section about what is the "unit" possible enums. or what is the unit of "period" exactly? or what is "admission", "subscription", and "publication". Just some more explanation on this section. (I think in the future we can integrate the paid relay concept in the protocol layer, but these steps are needed before!)
If you think these are logical, or any changes needed, let's discuss, after that I'll make PR and add them to NIP-11.
I was reading NIP-11 and I reached out maybe we can change and add some stuff there. Here are the details.
wildcard
: For fields likerelay_countries
,language_tags
, andtags
we can support"*"
as a valid value which indicates that all possible values are supported/applied. Or maybe the absence of these fields means the same thing? Or at least we have to make it clear what should they do to say we don't have it at all, we have specific ones, or we support/have all of them. or what behaviors can mean these?Pay-to-relay
: We need to add details in this section about what is the"unit"
possible enums. or what is the unit of"period"
exactly? or what is"admission"
,"subscription"
, and"publication"
. Just some more explanation on this section. (I think in the future we can integrate the paid relay concept in the protocol layer, but these steps are needed before!)If you think these are logical, or any changes needed, let's discuss, after that I'll make PR and add them to NIP-11.