Martin Algesten
Martin Algesten
Further clarification. When we add/remove/re-add a mic track, we do the following operations on the chrome side: ``` trans = pc.addTransceiver(…) pc.removeTrack(…) trans.sender.replaceTrack(…) ``` The spec says `removeTrack` is equivalent...
`replaceTrack(null)` should not make transceiver `inactive`, but we can set direction to `inactive` manually in this case. Either way, `inactive` is not the same as `stopped`.
I'm new to embedded programming (trying out an stm32f10 nucleo board). `probe-run` seems like a great idea, and it appeared `defmt` goes hand-in-hand. However I stumbled straight away on that...
Hi @Urhengulas! Thanks for the kind words! I understand the motivation, and after working with defmt for a day, nothing was particularly confusing. Thanks! Would you be open for me...
I believe we are still waiting for a new release of rust-socks.
Can we solve this with feature flags? Keep `chunked_transfer` as a default dependency, but point out in the README that the project can't be MIT licensed if the dependency is...
Well. It won't be as good :) Chunked transfer is used in HTTP/1.1 when the length of a body is not known. Many requests would work without it, but not...
Sure. Let's do it.
Yeah, we quite pride ourselves on the `#![forbid(unsafe_code)]` at the top of the crate.
Yeah, we definitely want to do something like that. There has been some discussion about it before. https://github.com/algesten/ureq/issues/264