mirror of
https://github.com/nostr-protocol/nips.git
synced 2024-12-23 00:45:53 -05:00
renamed nip 74
This commit is contained in:
parent
be57590435
commit
962d800d6e
|
@ -1,4 +1,4 @@
|
||||||
NIP-443
|
NIP-74
|
||||||
======
|
======
|
||||||
|
|
||||||
Nostr Web Services (NWS)
|
Nostr Web Services (NWS)
|
||||||
|
@ -68,7 +68,7 @@ Sending a request to the following domain:
|
||||||
will create direct message events for public key `3ef54d9f7eaa3a6fafaea680b1d047248c93408776027317a9535a2056b2ef53` on relay `ws://0.0.0.0:7777`.
|
will create direct message events for public key `3ef54d9f7eaa3a6fafaea680b1d047248c93408776027317a9535a2056b2ef53` on relay `ws://0.0.0.0:7777`.
|
||||||
|
|
||||||
### Basic Control Flow
|
### Basic Control Flow
|
||||||
Unlike traditional TCP/IP communications that resolve a domain name to an IP address and establish a direct connection, NIP-443 leverages NOSTR relays as intermediate proxies for TCP communications.
|
Unlike traditional TCP/IP communications that resolve a domain name to an IP address and establish a direct connection, NIP-74 leverages NOSTR relays as intermediate proxies for TCP communications.
|
||||||
|
|
||||||
The client must send an encrypted direct message to the desired NOSTR public key, following the format outlined in the [Message Format] section.
|
The client must send an encrypted direct message to the desired NOSTR public key, following the format outlined in the [Message Format] section.
|
||||||
Upon receiving the message, the exit node will process the request according to the specified message type, facilitating communication between the client and the destination.
|
Upon receiving the message, the exit node will process the request according to the specified message type, facilitating communication between the client and the destination.
|
Loading…
Reference in New Issue
Block a user