Oleksii Lozovskyi

As for features, *the defaults* might change over time too so I guess it's still a good idea to keep an eye on `features.h` when reviewing the changes for the...

Hm... well, dunno. Maybe it's better play dumb and just restrict the architectures for now. From what I gather from the build logs, all 32-bit architectures are affected. Since SEXP_USE_IMAGE_LOADING...

I believe we should definitely move away from hardcoding IPv4 addresses in the code. Or at least replace `"0.0.0.0:0".parse().unwrap()` with `"[::]:0".parse().unwrap()`, as Linux/macOS/Windows network stacks allow accepting IPv4 connections with...

I'd like to take over pushing `permessage-deflate` through the WebSockets stack. Which review points have to be addressed in order to get this PR merged?

Thanks for the investigation and the patch, @djaffer! WasmThemis tests are currently failing for Node v16. I'd wait for that to be fixed first before merging this...

'kay, `master` should have WasmThemis build fixed by now. If CI tests pass, this should good to merge 👍

Thank you for your contribution, @djaffer!

Maybe this should be a catch-all clause in native code instead?.. I'm not sure what exactly causes the exception in the original issue, but adding random checks for empty values...

> You want to install themis which is statically compiled with some backend (openssl/boringssl) to not install openssl/boringssl to your system? This. It's about providing `libthemis-boringssl0` packages that ship Themis...

> openssl comes also with an extended X.509 API that it's not needed Modern linkers have a dead code elimination pass and are able to remove whatever code is unused...