Sean Oxley

Thanks for the clarification, my mistake. I think it would be helpful to have a quick bit about this in that section, perhaps reword it to: > Finding Bombchus will...

Ah, okay, I wasn't sure if it was okay to change the controlling mode at the point of receiving the answer, but I can see how it is. I might...

I'm having this same problem myself. My read of the situation is that we [always create sender reports](https://github.com/algesten/str0m/blob/main/src/streams/mod.rs#L451) in `handle_timeout()` when we have streams, but [only consume them if ICE...

Perhaps a bit tangential, but this is not the first time I've run into problems with stuff building up when the connection never establishes properly. Before, I had an issue...

> sessions should not start generating any feedback until we got ICE If that would significantly complicate the logic, another option is to generate the feedback anyway and just drop...

Using this workaround for expressing the client type: ``` type RedisClient = ReturnType; ``` does not seem to give a very good type. It's sort of like it treats nonexistent...

I tried using the pinned box workaround mentioned above. I was able to create the component itself that took the callback as a prop, but I wasn't able to invoke...

Here's the code I'm using, it's possible this can be improved on but it's getting the job done right now. ```rust use dioxus::prelude::*; pub type BoxedFuture = std::pin::Pin; pub type...