Danilo Bargen

I think I agree with @mitsuhiko.

I'd also +1 on [rust-native-tls](https://github.com/sfackler/rust-native-tls). Besides the advantages mentioned above it also seems to have a nicer API.

Another issue is building for iOS. It requires a static build of OpenSSL which is cumbersome. If I read [this](https://github.com/sfackler/rust-native-tls/blob/2a917521eaa1ce2100ddf9197c9e69b228c8d1a2/src/lib.rs#L120-L122) correctly, native_tls uses security framework on iOS instead of OpenSSL.

Sorry for the triple-post :) I'm not sure how much work it would be and I don't have much experience with TLS, but would you be willing to accept a...

I'm also affected by this, apparently there's really no clean way to detect connection errors (except measuring the duration between connect and disconnect). I tried to fix it, but didn't...

I'd go with the type returned by the API. If the API returns hex values, we could keep them in hex, it's a bit easier to handle. But converting everyting...

Ok, go for `bytes`!

For libraries, a fixed MSRV is very important if *users* of the library might want to guarantee a fixed MSRV. Authors of a GUI application that want the application to...

> if avoiding stabilised features for 18 months is a price worth paying Having a stable MSRV per semver version does not necessarily mean that you need to target an...

Thanks for posting this, @Changaco :) I wasn't aware of any translation feature. But in any case, I speach English, German, Spanish and some French. I want to be able...