NIP26: Clarify multiple delegations

[mjg-foundation]

NIP26 doesn't specify whether multiple sets of kinds with different created_at times can be delegated in one go, for example: nostr:delegation:477318cfb5427b9cfc66a9fa376150c1ddbc62115ae27cef72417eb959691396:kind=1&created_at>1674834236&created_at<1677426236&kind=2&created_at>1674834236 Could this be clarified? I've built this already with the assumptions:

• There will be at most one "created_at<", and at most one "created_at>", in each delegation string, which apply to all kinds included in the string.
• All "kind"s must come before all "created_at"s
• The "created_at>" timestamp must be less than the "created_at<" timestamp

cc: @greenart7c3 @sethforprivacy

[jimbojw]

Seems reasonable that there’s only one range of kinds per delegation. If a delegator intends different kind ranges for different created_at criteria, they could sign multiple delegations.