Consider migrating to `rustls-platform-verifier` from `rustls-native-certs`
rustls-platform-verifier is recommended over rustls-native-certs by the team maintaining rustls-native-certs. From the readme:
Instead of this crate, we suggest using rustls-platform-verifier, which provides a more robust solution with a simpler API. This crate is still maintained, but mostly for use inside the platform verifier on platforms where no other solution is available. For more context, see deployment considerations.
Migrating would also allow using the native-tls feature on android/ios, which are not supported by rustls-native-certs.
Is this something the tungstenite team would be interested in doing/receiving a PR for?
If that's the recommended approach, then I agree that it's a good idea to switch to rustls-platform-verifier!