As some of you know, when one is accessing a website that is neither localhost or HTTPs, the security context breaks and doesn't allow us to access the crypto object. This causes an error when booting up js-ipfs in a browser.
But if we could add support for secure web-sockets with either signed or self-signed certificates we would be able to circumvent the problem.
Having that said, it would be awesome to add support for secure web-sockets!
As some of you know, when one is accessing a website that is neither localhost or HTTPs, the security context breaks and doesn't allow us to access the
cryptoobject. This causes an error when booting up js-ipfs in a browser.But if we could add support for secure web-sockets with either signed or self-signed certificates we would be able to circumvent the problem.
Having that said, it would be awesome to add support for secure web-sockets!