nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-27 02:35:52 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

tid bit more

Browse Source
This commit is contained in:
Ross Bates 2022-12-30 08:01:35 -06:00
parent 6abc7ec18f
commit 5e654ad731
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
44.md
View File

@ -71,9 +71,9 @@ In the same post User A chooses the option to attach their current location (cre
}] }]
``` ```
Users A, B and C all share access to the same private relay which supports receiving and responding to `kind 4326` messages. Also at this point each client is able to filter for all public and private responses to the `kinda 1` note. When user A sends a `kind 4326` note that references `p` tags it can automatically generate a `kind 1` note for all parties. This is just an example, the client developers can customize the experience however it best suits the users. Users A, B and C all share access to the same private relay which supports receiving and responding to `kind 4326` messages. Each client is also still able to filter for all public and private responses to the `kinda 1` note using the same interface. When user A sends a `kind 4326` note that references `p` tags the relay can automatically generate a `kind 1` note for all parties to prompt or alert them. This however is just an example, the client developers can customize the experience however it best suits the users.
In this example user B & C are able to acknowldge and respond using only a `kind 4326` note sent over the same private relay. These responses can include their current location coordinates, as well as other any other related `p` tags such as the Coffee Shop or Park they're currently at. The location data is the response. Here user B & C decide to acknowldge and respond using only a `kind 4326` note sent over the same private relay. These responses can include their current location coordinates, as well as other any other related `p` tags such as the Coffee Shop or Park they're currently at. The location data is the response.
User B Response: User B Response:
@ -107,7 +107,7 @@ User C Response:
}] }]
``` ```
This is a basic example to demonstrate the `kind 4326` data structures and for showing how an initial handshake between peers over public and private relays would work. From this point forward the private relay now everything it needs act as a coordinator - potentially executing geofence and nearby queries on the notes, generating arrival estimates, routing suggestions, ride-share integration, etc.... There are many possibilties for client experiences that go beyond the scope of the NIP. This is a basic example to demonstrate the `kind 4326` data structures and for showing how an initial handshake between peers over public and private relays would work. From this point forward the clients and the private relay now have everything needed to work in coordinatation - potentially executing geofence and nearby queries on the notes, generating arrival estimates, status updates, routing suggestions, ride-share integration, etc.... There are many possibilties for client experiences that go beyond the scope of the NIP.
## Summary of Benefits ## Summary of Benefits