Some security requirements might be that a user must use system provided OpenSSL.
Added a new feature called openssl-vendored which uses openssl feature and also add the vendored flag.
Easy w...
> As it happens, someone just now submitted a PR to ureq that shows a slightly more elegant way of doing this.
>
> [algesten/ureq#866](https://github.com/algesten/ureq/pull/866)
>
> We can ha...
As it happens, someone just now submitted a PR to ureq that shows a slightly more elegant way of doing this.
https://github.com/algesten/ureq/pull/866
We can have a `vendored` feature flag th...
> Is this based on libwebrtc's loss_based_bwe_v2 (https://source.chromium.org/chromium/chromium/src/+/main:third_party/webrtc/modules/congestion_controller/goog_cc/loss_based_bwe_v2.cc)?
Yeah, i...
It's here https://chromium.googlesource.com/external/webrtc/+/14e2779a6ccdc67038ed2069a5732dd41617c6f0/modules/congestion_controller/goog_cc/loss_based_bwe_v2.cc#347
You can configure these over...
This enables an optimisation where we reuse allocations, see `Scratch` `src/packet/bwe/mod.rs`. They are only 64 bytes in size so it didn't feel like a problem to make them copy.
Maybe `Scratch...
Is this based on libwebrtc's loss_based_bwe_v2 (https://source.chromium.org/chromium/chromium/src/+/main:third_party/webrtc/modules/congestion_controller/goog_cc/loss_based_bwe_v2.cc)?
Thanks for the feedback @xnorpx. I really should've created this as draft since I'm still working on it. I don't expect big changes, but the crate level configuration is particularly unfleshed out
Maybe this should just be called `enable_bwe_loss` and we can not in the comment that it's experimental. Then, when it becomes stable, we can default it to on