Hi @JarenL you’re welcome. You don’t have to have a local node running for message relaying (on port 30303). There are several public nodes like that you can add manually, like this one advertised by @gballet above
https://github.com/invisible-college/democracy/blob/master/docs/WhisperExperiment.md#testnet
To get JSON-RPC / websocket access for API calls, like in the Javascript example above, it is best to run your own node, restricted to your own IP address to prevent spammers. However, you are welcome to use my nodes for testing and learning
https://github.com/invisible-college/democracy/blob/master/docs/WhisperExperiment.md#public-node
whisper/mailserver
for inspiration
@sudhaaddagiri I don’t know of a way, unfortunately. If you save the keyPairs externally, you’d want to re-import them too. Whisper’s design currently encourages generating lots of ephemeral keyPairs frequently, maybe even once per use. So if a node restarts, you as the receiver would have to check, and re-request any needed data from a sender, using a new keyPair.
Can you tell us more about what you’re trying to do?
cryptogoth
* Thomas Mullen (Gitter): great work. I was able to run your demo on my laptop locally. I saw whisper debug messages in the web console, but no WebRTC video.
I deployed your demo to netlify, but it depends on Whisper being accessed via wss://
https://demo-whisper.netlify.com/shh-signal.html
Does anyone know how to run a Whisper server that accepts public wss requests?
cryptogoth
> <@gitter_androolloyd:matrix.org> We build a poc for discovery called Eros for eth Waterloo v1, basically whisper nodes compute the request of the service a user needs storage was our example. So you could put an order book of what you’re willing to pay to have a service connection established.
very cool Andrew Redden (Gitter)
cryptogoth
is there a repo somewhere I could check out?