-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Waku relay (node): chat app example #15
Comments
Current status (#9):
Next steps:
|
@jm-clius Could you please clarify how you encode the date and username in the chat messages? |
|
Issue reported with nim-waku: waku-org/nwaku#439 |
Looks like the issue is indeed timing related: 9a5acdc |
when looking at
|
The sleep helped for a while but does not anymore. State of libp2p when it does not work:
|
Absolutely. Now that more than one Waku implementation will read |
Made of aware of some possible dial/subscribe timing issue on nim-waku. Using test suite to pin down the issue. It looks like the timing issues are actually on js side as when the |
Issue open to clarify expected behaviour: waku-org/nwaku#443 |
Problem
Demonstrate the usage of the js-waku relay API in a real example.
Solution
Build a terminal chat app compatible with the nim-waky chat2 example app.
Acceptance Criteria
Able to send and receive messages from the fleet using said app.
Steps
The text was updated successfully, but these errors were encountered: