Viewing profile — pthatcherg

I'm excited to see a major use of WebTransport!

Why don't you like libwebrtc? There's a lot of good stuff in there.

This is just an initial proposal, and probably will reduce down to one with developer feedback and implementation experience, which is normal for API development. Whether it's one …

I'm not sure what you mean. It does work without a domain name and SSL cert.

I did something similar a while back: https://github.com/pthatcherg/stunl

WebRTC (with p2p) was done within the W3C, as was a p2p QuicTransport. And this new API is similar to the open screen APIs that have been done in the W3C. So I'm pretty sure work l…

I was one of the original authors of the p2p QuicTansport API and the WebTransport API which is based on it. I've also recently discussed this new local p2p API with the authors. A…

The article's information about WebRTC is not accurate. You can do client/server WebRTC without a "signaling server". Just make the server do the signaling. It takes a few extra ro…

There's also WebTransport

From a server or a native client, you can send whatever RTP packets you want, but you cannot send whatever RTP packets you want from a web client, and you cannot have access to the…

It's shame it looks like web clients won't be able to connect to each other p2p. If it supported the use of ICE+DTLS+SCTP or even ICE+QUIC, then it web clients could join in. Or am…

So WebTransport does what you were proposing to do?

It started in the W3C and the IETF group was added later. But thank you for pointing out that a lot of effort is put into making these standards a joint effort across the industry.…

How would one add datagrams to WebSockets?

You can use ICE and QUIC together. That's what the original version of WebTransport did (back when it was called QuicTransport).

There's nothing stopping QUIC from being p2p. In fact, the original version of WebTransport was called QuicTransport and was p2p, but there was more interest in client/server use c…

It's been almost 3 years since I first presented on WebTransport + WebCodecs: https://youtu.be/VD5GBLBiSxo Live streaming was a motivating example for both of those, as you can tel…

That's correct. You can't mix without decrypting. Signal does not mix at the server because it can't. More info is available at my blog post about it: https://signal.org/blog/how-t…

Hey, I'm the author of the Signal blog post about SFUs. I have a few questions/comments: 1. I don't think there are many good open source SFUs to choose from. I know of 2, maybe 3 …

If you're main focus is to mostly receive 1-2 video streams while sending 0, then, yeah, I guess bundle vs non-bundle doesn't matter much. I'm pleasantly surprised to hear that 25 …

Oh, that's interesting. That's not as bad as I thought, although I am surprised that's the approach that was taken (unbundled). In that case, if you're relying on REMB from WebRTC …

Yes, you are right that there is also a simple loss-based congestion control mechanism ( https://github.com/jech/galene/blob/e8fbfcb9ba532f733405b1c5... ) and a min() between it an…

I was curious and looked through the code of Galene briefly and found the following, which may partially answer your question. For context, I am familiar with the Jitsi code and ha…

Yes, that's called "signaling". In the case of Signal, it's done through Signal messages, which pass through a server. But the server doesn't know they are calling related messages…

Yes, it knows the IP addresses of the clients. The other thing it knows is that you have provided a proof that you are a member of a the group conversation associated with the grou…