Pull request created for nostr-protocol/nips: #528
NIP-81 - Event Copy
--------------------
Please check the NIP for some use cases.
Pull request created for nostr-protocol/nips: #527
add nip101 - Alias exchange
--------------------
Alias exchange
Pull request created for nostr-protocol/nips: #525
Idea, add "name" tag to channel create
--------------------
It's probably going to be very helpful to search for channels by name. Placing a recommended "d" tag, so a user can search channels by name would probably be helpful in chat implementations.
Pull request created for nostr-protocol/nips: #501
NIP-84: Highlights
--------------------
This NIP introduces `kind:9802` Highlight event as implemented by https://highlighter.com and https://habla.news
`kind:9802` events are highlights of nostr events' `content` (e.g., `kind:1` or `kind:30023`) or URLs, signaling content of importance to a user.
NIP text: https://github.com/pablof7z/nips/blob/highlights/84.md
@fiatjaf @verbiricha
Pull request created for nostr-protocol/nips: #242
NIP-07: Add NIP-26 createDelegation function
--------------------
In order to implement [NIP-26](https://github.com/nostr-protocol/nips/blob/master/26.md) by way of [NIP-07](https://github.com/nostr-protocol/nips/blob/master/07.md), a createDelegation function needs to be exposed by the NIP-07 extension.
Pull request created for nostr-protocol/nips: #163
NIP-11 extension for Relay Limitations
--------------------
This PR is an extension to NIP-11 and allows the relay to specify its technical, and other, limitations so that clients can adjust their behaviours to better suit the relay.
This includes such things as:
- maximum length of incoming JSON (which has many impacts)
- retention times for specific event types
- political considerations
- content policies
To be very clear: this document DOES NOT propose any values for these limitations. It is merely a way for cooperating clients to know what they are dealing with. All are optional fields.
This PR could be merged into NIP-11 as it is a pure extension to that JSON response, or be its own thing. I'm proposing 111 as its number in that case.
Pull request created for nostr-protocol/nips: #85
NIP-37: Remote signing of events
--------------------
NIP: https://github.com/nostr-protocol/nips/blob/remote-signing/37.md