Native https/wss support

Wider wss transport support by ipfs nodes is needed for making in browser applications more viable. Currently these nodes are incredibly rare. I have scan set with over 1 M random ipfs nodes and not even 10 supports wss. ws transport supports 60.

Deploying WSS using reverse proxy complicates infrastructure, percentage of people willing to do that is much less then when this feature is built in and enabled by default.

It will be much better to have internal support for https - it is pretty common between web frameworks today. Go supports https and ACME Client Implementations - Let's Encrypt ACME for getting certificates is supported as well.

You may be interested in Proposal: Improved Browser Connectivity using Secure WebSockets · Issue #1331 · libp2p/go-libp2p · GitHub.