diff options
| author | fiatjaf <fiatjaf@gmail.com> | 2026-03-03 22:58:56 -0300 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2026-03-03 22:58:56 -0300 |
| commit | 79399703d72b896dea4c256262983745be0a2c33 (patch) | |
| tree | c6113b1c21f9054fbc062519e807379ba989b3ea | |
| parent | ed77351a2b151464619e23c5c0f1bc47f08601d6 (diff) | |
empty livekit support signaling handler.
| -rw-r--r-- | 29.md | 2 |
1 files changed, 2 insertions, 0 deletions
| @@ -60,6 +60,8 @@ Relays should enforce access control at the LiveKit JWT creation time according | |||
| 60 | 60 | ||
| 61 | Relays MUST set the `sub` property on the issued JWT (called "identity" in the standard LiveKit libraries) to the requesting user's lowercase hexadecimal public key. | 61 | Relays MUST set the `sub` property on the issued JWT (called "identity" in the standard LiveKit libraries) to the requesting user's lowercase hexadecimal public key. |
| 62 | 62 | ||
| 63 | In order to inform clients about relay support for AV (so they can display that option for users when creating or editing groups) relays should serve a status code `204` at `https://relay.tld/.well-known/nip29/livekit`. | ||
| 64 | |||
| 63 | ## Event definitions | 65 | ## Event definitions |
| 64 | 66 | ||
| 65 | These are the events expected to be found in NIP-29 groups. | 67 | These are the events expected to be found in NIP-29 groups. |