nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-28 11:15:50 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

room identifiers

Browse Source
This commit is contained in:
Jack Chakany 2023-03-13 20:11:27 -04:00 committed by GitHub
parent aadc197e88
commit 7bad8685b3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 15 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
100.md
View File

@ -1,9 +1,11 @@
# NIP-100 # NIP-100 WebRTC
## WebRTC
`draft` `optional` `author:jacany` `draft` `optional` `author:jacany`
This NIP defines how to do WebRTC communication over nostr This NIP defines how to do WebRTC communication over nostr
## Defining Rooms
Rooms are essentially the space that you will be connected to. This must be defined by a `r` tag following the pubkey of the person you are connected to or some other identifier (maybe a lobby id for a joinable voice channel, etc.)
### Broadcasting that you are present ### Broadcasting that you are present
Announces that you are here, and ready to connect to others. Announces that you are here, and ready to connect to others.
The connection ID is inferred from the provided pubkey. The connection ID is inferred from the provided pubkey.
@ -12,7 +14,8 @@ The connection ID is inferred from the provided pubkey.
"kind": 25050, "kind": 25050,
"pubkey": "<sender pubkey>", "pubkey": "<sender pubkey>",
"tags": [ "tags": [
["type", "connect"] ["type", "connect"],
["r", "<room id>"]
] ]
} }
``` ```
@ -23,7 +26,8 @@ The connection ID is inferred from the provided pubkey.
"kind": 25050, "kind": 25050,
"pubkey": "<sender pubkey>", "pubkey": "<sender pubkey>",
"tags": [ "tags": [
["type", "disconnect"] ["type", "disconnect"],
["r", "<room id>"]
] ]
} }
``` ```
@ -36,7 +40,8 @@ Used when responding to a `type:connect`. Offering to connect to that peer.
"pubkey": "<sender pubkey>", "pubkey": "<sender pubkey>",
"tags": [ "tags": [
["type", "offer"], ["type", "offer"],
["p", "<reciever pubkey>"] ["p", "<reciever pubkey>"],
["r", "<room id>"]
], ],
"content": { "content": {
"offer": "<offer>", "offer": "<offer>",
@ -52,7 +57,8 @@ Used when responding to a `type:connect`. Offering to connect to that peer.
"pubkey": "<sender pubkey>", "pubkey": "<sender pubkey>",
"tags": [ "tags": [
["type", "answer"], ["type", "answer"],
["p", "<reciever pubkey>"] ["p", "<reciever pubkey>"],
["r", "<room id>"]
], ],
"content": { "content": {
"sdp": "<sdp>", "sdp": "<sdp>",
@ -68,7 +74,8 @@ Used when responding to a `type:connect`. Offering to connect to that peer.
"pubkey": "<sender pubkey>", "pubkey": "<sender pubkey>",
"tags": [ "tags": [
["type", "answer"], ["type", "answer"],
["p", "<reciever pubkey>"] ["p", "<reciever pubkey>"],
["r", "<room id>"]
], ],
"content": { "content": {
"candidate": "<sdp>", "candidate": "<sdp>",
@ -77,4 +84,4 @@ Used when responding to a `type:connect`. Offering to connect to that peer.
} }
``` ```
Essentially, just directly feed what comes out of the WebRTC functions straight into the `content` field. It makes things cleaner and easier. Essentially, just directly feed what comes out of the WebRTC functions straight into the `content` field. It makes things cleaner and easier.