NIP-AC: P2P Voice and Video calls over WebRTC#2301
NIP-AC: P2P Voice and Video calls over WebRTC#2301vitorpamplona wants to merge 1 commit intonostr-protocol:masterfrom
Conversation
|
Noscall is also doing P2P calls @sanah9 |
|
If I open the app and answer a voice call ~20 seconds after the offer was sent, should Call ICE Candidate events (kind 25052) ever be dropped by the staleness rule? |
|
I just ignore it, together with ignoring the same event from any relay that might keep these ephemeral giftwraps. But i am happy to change if it makes the ux better |
|
This seems at least somewhat with #2238. I don't know anything about the details, but livekit works well; it would be nice to use the same standard for calls as much as possible, and using livekit would reduce NIPs surface area. @mplorentz @fiatjaf |
|
For LiveKit to work, we will need to have a "Blossom"-like spec list for it. With users picking the servers they like to host conversations, etc. We might still keep P2P for the super private comms. |
|
Has Amethyst already implemented this NIP? Which app can I use to test it? |
|
We are still finishing it... WebRTC is tricky to get right |
I think 20 seconds is a bit too short for answering a call. How about extending it to 1 minute? |
This is an expansion of the original NIP-100 (implemented by 0xChat etc) to:
It was written to follow Amethyst's recent implementation, and it is not backwards-compatible.
This NIP should also not be used for any other kind of P2P communication. It is specifically designed for voice and video calls.
Finally, I added a session on Test vectors that, when complete, will make it fully compatible with Amethyst's calling features.
This entire NIP wasn't designed for humans to code, but for AI to read and have the complete set of instructions to one-shot it.