hossameldeen / whisper-cli-chat Goto Github PK

Currently, all logging is done through console.log, turning it on & off through commenting & uncommenting.

• When logging process is chosen, ctrl+shift+f 'console.log'.
• Remember to check logs of test code as well.

An issue for tracking places where in code that retrieve remote resources & these remote resources may be different depending on when the command is run.

• Of course, in package.json.
• The FROMs in Dockerfile.
• The git clone in Dockerfile.
• The apk add in Dockerfile. --no-cache has no effect on docker cache.
• The apt-get update && apt-get install ... in Dockerfile. Again, this has no effect on docker cache. Docker cache makes a string comparison.

Currently, we're dealing with version locking in an inconsistent way: sometimes we lock against a certain version & sometimes we don't. No decision has been taken yet for which direction to go.

There must be some way of peer discovery in any decentralized. In Whisper, this peer discovery is done through peers connecting to a so-called boostrap node.

For the purposes of the chat-app task, the 2 peers need a bootstrap node to discover each other/to be part of the same whisper network. There're 3 options for such bootstrap node:

1- Use a publicly-available one.
2- Create a public server dedicated for the chat app.
3- Make one of them act as the bootstrap node.

For 1: couldn't find one that is working (didn't look much). Also, I expose the peers' IPs to this public one & don't know if it's evil. Not worth it especially it's just a PoC.

For 2: fakess.

For 2 & 3, especially 3: since the numbers of users is too low (just them in 3), I think all advantages of Whisper are practically lost.

For 3: a bit negative UX for requiring one of them to enter the IP/some info of the other.

Since it's a PoC (Proof-of-Concept) & we don't want any kind of risk, will go with 3.