Alejandro Pascual

Hi, I'm trying to use the ORTC API to create an `RTCRtpSender`, but the [ORT example](https://github.com/webrtc-rs/examples/tree/main/examples/ortc) only covers the `RTCDtlsTransport`. The API requires me to pass an interceptor to `new_rtp_sender(...)`,...

I would also appreciate a more ergonomic API.

Hi @stammw, Thanks for looking into it. I agree that this should not be part of the core of H3 and that it makes sense to delay this until the...

Hi, I'm trying to build a server that supports WebTransport clients, which is a use case that might become more popular with the release of WebTransport in Chrome 97. Good...

I believe that no additional work is required to support WebTransport, but I might be wrong. I just wanted to let you know because there might be more people looking...

I can confirm that this is still an issue in `0.19.0`, and indeed looks like a bug in the debug-renderer.

I have a similar problem and am able to manually fix it by replacing ```rust from = "Column::SampleId", to = "super::samples::Column::ProjectId", ``` With ```rust from = "(Column::SampleId, Column::ProjectId)", to =...

@alice-i-cecile I don't like/understand indexing systems by their sets. I like the idea of moving systems out of schedules and into a centralized system registry, but IMO it should only...

I'd like to unify the following commands: ``` rust pub struct RunSystemCommand { _phantom_marker: PhantomData, system: S, } // formerly RunSystemsBySetCommand pub struct RunCallback { pub callback: Callback, } ```...

@alice-i-cecile I have another question. #4090 stablishes as future work: > Use this API to store all systems, regardless of whether or not they belong to a schedule, and solve...